-
Try CliSecure, a .NET obfuscator and code protection tool by SecureTeam. You may find it here: http://www.secureteam.net It's only 299$ for the express edition, it might worth your time and effort developing your own solution.
-
Another obfuscator which gives good protection to your .net assemblies is Crypto Obfuscator ( http://www.ssware.com/cryptoobfuscator/obfuscator-net.htm )
-
Some people are concerned that IL doesn't offer enough intellectual property protection for their algorithms. In other words, they think that you could build a managed module and that someone else could use a tool, such as an IL Disassembler, to easily reverse engineer exactly what your application's...
-
You can use the obfuscator that's built into ASP.NET 1.x and above, or you could use one of these 3rd party obfuscators which generally claim to be better: http://www.lesser-software.com/ilobf.htm http://www.junglecreatures.com/DesktopDefault.aspx http://www.9rays.net/cgi-bin/compone...i?act=1&cid...
Page 1 of 1 (4 items)