To integrate Code Protection with Visual Studio or automated builds you must first create a configuration file that will be used by Code Protector to control the protection process.
While it is possible to specify the methods to be protected in the configuration file the recommended approach is to select the methods declaratively in source code as outlined Select Methods to be Protected. This approach ensures the selected methods can be changed without the need to update the configuration file.
To create a configuration file
- Launch Code Protector and login to the Software Potential service
- Click the Project tab, and then click View.
- Add the modules/assemblies to be protected/licensed
- Select the Permutation to be used in the Permutation drop down list
- Select the runtime variant to be used in the Runtime/Agent Variant dropdown
- Standard - this version should be selected if you do not wish to use Distributor to implement floating licensing models
- Distributor - this version should be selected if you intend to use Distributor
- The settings apply to the entire project, the application, and the methods selected for protection. Settings are displayed in the right portion of the page in the Project view. For more information about selecting the settings, refer to the Code Protector User Guide.
- Click File, and then click Save Project As…
- Select the folder where the .csproj file is located
- Name the file the same as same as the cs/vbproj file, but with a .SLMCfg extension i.e., <ProjectName>.SLMCfg.
- Click Save to create a configuration file <ProjectName>.SLMCfg alongside the corresponding .vbproj/.csproj file.
In order for the protection to apply correctly, the location of the configuration file should not be changed relative to the protected and unprotected assemblies. If the configuration file is not stored on the same drive as the input assemblies, the complete physical path for the input as well as output directory is used within the configuration file, to reference these files.