C# code Protection Using .NET REACTOR

The assembly (.exe, .dll) etc we build using .Net Framework  can be decombiled using visual studio command Promt.  ildasm is the commad that we can use to open an assembly as Resource hacker is doing.

C:\Program Files\Microsoft Visual Studio 9.0\VC>ildasm


This will Pull up ILDASM window for us.

This is the General Structure of a .net Assembly

So select the exe file from the File menu in that. We can see the decombiled file as shown

Thus our Function and code Assembly are visible to Others. To over come this issue we combile that code using .NET Reactor.



.NET Reactor is a powerful code protection and software licensing system for software written for the .NET Framework, and supports all languages that generate. .NET Reactor prevents decompilation by a variety of methods which convert your .NET assemblies into processes which no existing tool can decompile ( and which are also very likely to prevent decompilation by any future tool). .NET Reactor builds a native code wall between potential hackers and your .NET assemblies by producing a file which cannot be understood directly as CIL. Because the CIL in your assembly is emitted intact only at run time or design time (in a form in which the source is completely inaccessible), no tool is capable of decompiling .NET Reactor protected assemblies. The native code wall created by .NET Reactor between the hacker and your source includes industry leading NecroBit technology, which is exclusive to .NET Reactor. .NET Reactor's protection has never been broken since the first release in 2004. These technologies make reconstruction of your source code more difficult by so many orders of magnitude that NecroBit is by far the most effective protection you can use for .NET assemblies. In addition to industry leading intellectual property protection, .NET Reactor provides powerful options for securing you revenue stream by enforcing licensing terms with a rich variety of trialversion and full version locks. .NET Reactor offers you an easy and reliable way to: - Secure your .NET applications and .NET libraries - Replace CIL code with native code - Perform additional layers of protection, including obfuscation - Merge assemblies, and - Protect your revenue by enforcing trial version restrictions and full version licensing terms.