Geek Answers Handbook

I release my software. Should I use obfuscator.net?

I plan to release an alpha version of my free closed-source software in the near future (this is a development tool written in C #), do I need to use .net obfuscator?

In general, I would not want people to easily view the code and, most importantly, modify it.

(I'm afraid I'm not ready to open it at this point in time.)

If I really need to use an obfuscator, would you suggest that it does a “good enough” job, and, preferably, integrates with MS Visual Studio (automatically gets confused at release)?

+4
source share
3 answers

If you mess up your code, you will slow down and possibly discourage anyone who might try to reverse engineer it.

If you do not, you can also make it open source.

This is your choice - you have nothing to lose by confusing it.

Dotfuscator Community Edition is part of Visual Studio these days, and it will do the bulk of the work (although obviously you need to pay if you want all the bells and whistles), or there are a number of free / shareware options if you do a search .

+3
source

I would not bother. Anyone who is going to solve this problem will find a way, and other users will just want something that works, and do not care or do not want to know what the code looks like.

However, the version of the dotfuscator community is very limited. I heard that the pro version is good, but did not play with it.

+3
source

Yes, you need to use an obfuscator if you do not want others to see your code.

Crypto Obfuscator can do the job well, and integrates with Visual Studio through MSBuild.

+1
source

More articles:


All Articles