DNGuard HVM - Protect Your .NET Code

DNGuard HVM is a .NET obfuscator and code protector that offers protection against reverse engineering of your code. This tool implements a unique code protection technology that blocks attackers from utilizing advanced code tampering techniques such as dumping assembly contents from in-memory, catching methodbody from JIT-compilation. Learn More...



Best code protection technology available

Compared with other code protection tools available in market today, DNGuard HVM is offering the highest level of expertise as far as code protection is concerened. Opposed to other code protection tools your code remains protected at all times even when it's resident in memory.

Support Windows Forms applications, Component developers, and ASP.NET applications.

The protection scheme employed by our product generates valid .NET assemblies, Class, method, and other symbol names are kept intact thus ensuring that your code behaves exactly the same as the original. The hosting environment is not restricted by any means, this makes DNGuard HVM the perfect choice for component developers, Asp.net applications as well as winforms based applications.

VC++ .Net full support

DNGuard HVM can be used on projects that contain mixed images (generated by VC++ .NET).

String encryption

String encryption 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 that embedded decryption method..

Resource Protection

Resource protection prevents icons, images, strings and other managed resources in MSIL code from being viewed. Our protector is the only product that offers such a feature.

Licensing Management Support

DNGuard HVM provides a pre-defined security callback function that allows custom licensing code to be integrated into the protected code. This function will be invoked before any application code execution. When it fails, code will still be protected, and there is no way to execute the application code, which is ideal to implement trial versions for .NET software.

Free obfuscation feature included in the trial version

If you desire to completely eliminate the metadata information stored in your assemblies such as class and methods names you can do so using the obfuscation capabilities offered by our product. Declarative obfuscation using standard custom attributes allows you to enforce restriction on classes or methods that you don't wish to obfuscate or would like to ensure that they will get obfuscated. This is done by annotating your code using the System.Reflection.ObfuscationAttribute on types and their members which tells DNGuard HVM how to obfuscate them. It will allow you to enforce a restriction on a single class or method as well as enforcing one to a class and all its members. Renaming scheme support usage of Unreadable chars as well as standard renaming scheme. Our obfuscator is offered for free and if you choose only to obfuscate your code no licensing restriction will be enforced on the obfuscated assemblies.

GUI and Command Line Interface

DNGuard HVM is extremely easy to use. The application takes one or more assemblies and generates their protected equivalents instead of the originals or creates them at a specified location. Command line interface enables you to seamleslly integrate DNGuard HVM with your build server.

Framework 1.0, 1.1, 2.0, 3.0, 3.5, 4.0, 4.5, 4.51, 4.52, 4.6 Support

Support for all versions of the .Net framework including version 3.0, 3.5, 4.0, 4.5 the framework that ships with windows vista, Windows Server 2008, Windows 7, Windows 8, Windows 8.1, Windows 10. 

X64 platform support, IA64 Platform compatible

Our code protection tool run on windows operating system and includes support for the x64/IA64 platform.

No Runtime Discrepancy

DNGuard HVM supports standalone applications (.exe) as well as class libraries (.dll), such as ASP.NET, Windows Form Controls, Web Components, Windows Services, Web Services, etc. In all situations, the protected code behaves exactly same as the original at design time and runtime, and there is no reflection-related problems that obfuscators have to deal with. No configuration file is required.