In this section we discuss which Files To Deploy with your licensed software, how you should go about Creating Your Installer, as well as several categories of special deployment considerations, including:

• Machine Locking Considerations

• Tamper Resistance Considerations

• Target Operating System Considerations

• Windows Permissions and Security Considerations

• Possible Conflict Considerations

In general, however, deploying the license for your application is relatively simple and involves two or three main steps:

1. Your installer package must put the distributed license file (Main License File) in a location that can be determined by your application either in absolute terms or relative to the host applications directory. For simplicity we recommend that you deploy it to the same directory as the host application executable. (See the StartUp function in the ClientProtector Reference for information about relative vs. absolute paths of the Main License File.)
   
   Note: the Main License File must be deployed on the client machine.  It is not supported to deploy the Main License File (or the application itself) to any other machine through either a UNC path or a mapped drive.

2. Your installer package must register the SSCProt.dll with the Windows system, and (as usual) it can deployed in the directory where you would normally place shared components or dlls. (See your installers documentation for instructions how to register dlls).

3. If you use a steganographic alias file with your license, your installer package must put the original bitmap file inside the same directory where you chose to place the Main License File. Again - for simplicity, we recommend that you deploy this and the Main License File to the same directory as the host application executable.

To create a distributed license file, you must first compile your license. Make sure you have read Compiling a License.