Features

• Protection against decompilation. The protector prevents your assemblies from being decompiled by any .NET decompiler.
• Protection against disassembly. The protector prevents ILDASM and other disassemblers from disassembling your .NET code.
• Support .NET exe and dlls, such as Windows Forms applications, Controls, and ASP.NET code-behind dlls.
• Replacement of MSIL code with native code provides the same level of protection as native C/C++ code.
• MSIL code and native code encryption provide additional protection.
• String protection prevents the viewing and searching of any literal strings such as user id or special keys that may be found in MSIL code. The implementation is secure and no extra instructions are introduced. In contrast, obfuscators inject a decryption method immediately after each string which allows a hacker to easily retrieve strings by invoking the embedded decryption method.
• Resource protection prevents icons, images, strings and other managed resources in MSIL code from being viewed. Our protector is the only product that offers this feature.
• Password protection allows a password to be assigned to your program, and a user must type the correct password in order to execute your program.
• Security callback mechanism allows custom licensing code to be integrated into the protected code.
• Intact metadata. Class, method, and other symbol names are kept unchanged, and thus no reflection-related runtime discrepancy that exist in the case of obfuscators. Components at design time behave exactly same as the original.
• No runtime discrepancy, protected assemblies behave exactly same as the original in all situations it supports.
• Support mixed images that contain both managed and unmanaged code. Almost every image produced by Visual C++.NET belongs to this category.
• Extremely easy to use, the protector takes one or more .exe and .dll files as input, and transforms them into new format either in place or save as different file names. No configuration is required. No extra steps are involved. No third party tools are needed.
• Advanced GUI, highly integrated with Remotesoft .NET Explorer.
• Seamless integration with Microsoft Visual Studio .NET through an addin. Protection can be performed within the same IDE, and can be added into the automatic build process.
• ASP.NET is supported.
• Microsoft All .NET Framework versions and service packs, .NET 3.5, 3.0, 2.0, 1.1, 1.0, are supported.
• Version independency. You can choose to generate the same protected code that runs on Microsoft .NET Framework 1.0, 1.1, 2.0, 3.0, 3.5 and different service packs.
• Small runtime component needs to be distributed with the protected code, but future version will eliminate this runtime component.
• Protected code runs only on Windows platforms.