.NET 2.0 and later projects are supported, however the DeployLX tools themselves require at least .NET 3.5.
| Component | Framework Compatibility |
|---|---|
Licensing RuntimeThe DeployLX.Licensing.v5.dll licensing runtime is distributed with your application and is used to the license restrictions on the use of your software. |
2.0, 3.0, 3.5, 4.0, 4.5 |
License Servers and Management RuntimeThe DeployLX.Licensing.Managment.v5.dll management runtime is used by the license server and for e-commerce integration. |
2.0, 3.0, 3.5, 4.0, 4.5 |
Network Licensing RuntimeThe DeployLX.Licensing.Nlm.v5.dll network runtime, network monitor and administrative tools are distributed with your application. |
3.5, 4.0, 4.5 |
64-bit native versions of the licensing runtimes can be found in the Redistributable\Any CPU folder. The Any CPU files work on both 32-bit and 64-bit platforms but have not been encrypted, they are obfuscated only.
The Licensing and Management runtimes require unmanaged code permissions. This is the default for Full Trust environments. Other environments will need additional configuration. See Full Trust Required for ASP.NET for details.
The assembly analysis system used by DeployLX CodeVeil requires a fair amount of memory to resolve all the project inter-dependencies. The exact amount of required is difficult to estimate but you can expect between 25-40MB for each assembly included in the project and 10-25MB for each assembly referenced by project assemblies. If more than one project assembly reference the same 3rd party assembly (ex. System.dll) it is only loaded into memory once.
DeployLX CodeVeil adds extremely powerful runtime protection features to your assembly when it is veiled. These features do impose some additional runtime requirements on your assemblies when you deploy them to your customers. Some features will also require Full Trust for your assemblies on the target machine.
This chart will help you determine which additional requirements you will need to be aware of. See the Planning a Project to be Protected topic for details setting up your project.
| Feature | Full Trust | 32-Bit | 64-Bit |
|---|---|---|---|
Obfuscation |
|||
Obfuscate Everything! |
|||
| Anti-Debugging, Anti-Profiling, Anti-Modification | |||
| String Encryption | |||
| Resource Encryption & Compression | |||
| Code Encryption | |||
| Assembly Compression | |||
| Assembly Bundling |
64-bit assemblies are not supported in combination with the Code Encryption and some of the advanced runtime protection features. You can run a veiled assembly with encryption on a 64-bit operating system but the application itself must target the 32-bit subsystem.
The Code Encryption and Anti-Cracking features rely on a native runtime executive that loads and manages the execution process of a veiled assembly. This native executive adds additional security requirements and limitations to the end-user's machines. For standard Windows Applications and Services this will have no effect since they are granted Full Trust by default. However, if you are running your application from a network share or you are protecting an ASP.NET application you will need to explicitly grant Full Trust to your assemblies or omit the use of these advanced features.
DeployLX CodeVeil's runtime encryption support is not compatible with .NET 4.5 or .NET 4.0 systems that have .NET 4.5 installed. We recommend using Obfuscate Everything with Zero Width String renaming to achieve near encryption with 100% managed code.