DLL protection

Question

Quite a few people really showed interest in dll ivé, sent them, and they are not the type that you need to give away for free too often ...

I'm just wondering if I will sell my components, user controls, etc., how would I protect them, in terms of ownership / encryption code (if possible), etc. What steps do / b> have to help people using yours not to pay for them?

Answer 1

You can use any commercial obfuscater that encrypts your functionality and gives an error if you decompile.

Here I have the entire list that is available in the market. I used many of them, some of them simply encrypt the string, the public method, private methods, properties and all. Just go through it.

view the entire list and article

Answer 2

The only truly safe way to protect your DLL is to not let them. Expose it instead through a web service, etc. (Obviously, this does not work in all cases). Every obfuscator can be broken with patience. Think about how much the gaming industry spends on it and things are broken / remodeled in a few days, sometimes hours.

Lawyers can serve as a layer of protection, and obfuscation will certainly prevent downtime. But a certain hacker (for example, for commercial illegal espionage) will be able to get your code in the end.

I think you just need to weigh the costs and benefits ...

Answer 3

Well, I will definitely return my copy, company name and production name to my DLL. Whenever someone uses it, this information still appears in my DLL. And if possible, I will try to use the Dotfuscator tool from visual Studio, which helps obfuscate my DLL.