Settings Menu— .NET Directories Tab
The .NET Directories tab enables you to view and modify the directory paths that Sentinel LDK Envelope searches by default for .NET assemblies. The directory paths are required, for example:
>If you installed a later version of .NET Framework. (Sentinel LDK is installed with .NET Framework version 2.0.) In this case, you must indicate where the .NET Framework assemblies can be found.
>If the protected application requires access to other (unprotected) assemblies.
| Assembly search paths | Displays the currently defined directory paths that Sentinel LDK Envelope will search for .NET assemblies. |
Click the Add button to browse to and add a directory to the list. Select a directory and click Remove to remove a directory from the list.
NOTE You can override the default directory paths for a given .NET program. Specify an alternative list of directory paths on the .NET Directories tab for the specific .NET program.
Note the following:
>The default .NET Framework search works well and does not require that you specify any path manually.
>The main purpose of these paths is to supply additional path to .NET DLLs for customer apps, when these DLLs are located in separate folders.
>Thales recommends that you not specify a path at all if protection works well. Only specify paths if Envelope cannot locate some dependency (a customer DLL or system DLL).
>The Assembly search paths list should not be used to select the path to .Net Framework. If the list is used for that purpose, the following occurs:
a.When several paths are supplied (for example, paths to .NET 2.0 and .NET 4.0) – Envelope uses only the first path. Any other path is ignored.
b.If the version of .NET Framework in the specified path is later that the version than is required by the app, the application will be upgraded to the later version.
c.If the version of .NET Framework in the specified path is earlier that the version than is required by the app, Envelope does not accept the application for protection.
NOTE Changes to the paths on this page are not possible once you have added the first application to Envelope. To make changes to the path at that point, it is necessary to restart Envelope.
Envelope binds permanently to the Framework version during the work session based on the first application protected. As a result, any other file protected during current session will be bound to same Framework version. If you want to protect applications with a different framework version, you must first restart Envelope.