Protection Settings Tab for .NET
To display this tab, select the relevant .NET program file in the navigation pane. On the Edit Protection details screen, select the Protection Settings tab.
The Protection Settings tab for .NET displays the protection settings for the relevant .NET program file.
The default values for the protection settings are taken from the Project Protection Settings Screen for .NET.
If you want to override any of the default settings, select the check box for the relevant setting and then modify the setting value as required.
The Protection Settings screen contains the following settings:
| Setting | Description |
|---|---|
|
Apply Compression
|
Enables you to designate the compression level of protected classes. Protected classes can be stored in the output file with the following compression levels: |
|
>Off - No compression is applied. |
|
|
>Low - Fast compression process. |
|
|
>High - Slow compression process. |
|
|
NOTE Selection of a compression level does not affect the speed of the decompression level. |
|
|
Obfuscate Symbols
|
An anti-reverse engineering security measure that enables obfuscation of the .NET assembly’s symbol names. Names become arbitrary strings containing random letters or numbers. Select one of the following levels of symbol obfuscation: |
|
>Off - No obfuscation is applied. |
|
|
>All symbols - Full obfuscation. This is the default protection level. |
|
|
>Exclude resources - Does not change the names of resources. Use this option in the case in which you are unable to protect .NET assemblies with theAll symbolsoption. |
|
|
Note that symbol obfuscation can cause issues when class names or method names are used externally as references but cannot be found because they might be obfuscated. This happens, for example, if your project uses external configuration files with class names as references. In these instances, you must identify such dependencies themselves and either select the Exclude resources option for the Obfuscate Symbols setting or completely disable symbol obfuscation for these classes and methods. Envelope attempts to detect external references where obfuscated names could cause problems. In these instances, Envelope automatically disables the obfuscation of the specific symbols. NOTE You can obfuscate the entire code of specific methods in an assembly via the Protection Details pane. |
|
| Integrity Protection |
If enabled, the protected application is signed with a digital signature. At run-time, the signature is checked to ensure that the code was not modified. Program integrity protection is compatible with Microsoft Authenticode signatures. It is possible to apply a Microsoft Authenticode signature to the protected application when the Integrity Protection option is enabled. |
|
String Encryption |
Enables string encryption for your .NET assembly |
| Encrypt New Methods | When you load a changed binary to an existing Envelope project, Envelope uses default settings to select which of the added methods to protect. If you enable this setting, Envelope selects all of the added methods for protection. |
| Message Output Mode |
Enables you to select how run-time user messages are provided. The following options are available: >Windows displays messages in a message box. >Event Log includes events related to running the protected program in the Windows Administration Tools Event Viewer utility. >Stderr displays messages to a user running Sentinel Envelope from a command-line. By default, only the Windows option is selected. |
| Strong Name Key File |
Select the check box and select a strong name key file if you want to sign the .NET assembly automatically following Sentinel Envelope protection. For more information, see .NET Considerations. |
| Assembly Search Paths |
The directory paths that Sentinel Envelope
will search for .NET assemblies. Click |

to add a path to the list.