How to deploy your protected .NET applications:
When deploying applications containing ProtectKit.NET
functionality, the following files must be deployed with the
application.
For 32-bit applications
1. Newtone.ProtectKit.Win.Password.dll (ProtectKit.NET
assembly)
2. ProFuncNET.dll (the ProtectKit.NET password protection function
DLL). For added protection, it is recommended that you rename this
file.
3. ProInfo32.dll (the file where protection information is stored).
For added protection, it is recommended that you rename this
file. To rename the ProInfo32.dll file, use the Set Password
Protection tool (ProtectKit.NET) and choose the "Save As"
option.
4. DdScm32.exe or the DdScm64.exe (which file will depend on the
operating system environment where the application is to be
installed. The DdScm32(64).exe must be registered.
If you are not sure of the operating system environment (whether 32 bit or 64 bit OS) then deploy all three files DdScm.exe, DdScm32.exe, and DdScm64.exe. (Internally, the DdScm.exe will determine the operating system and execute the proper program). In this case, the DdScm.exe, must be registered. For details about registering DdScm.exe, DdScm32.exe, or DdScm64.exe, see Options for DdScm.
For 64-bit applications
1. Newtone.ProtectKit.Win.Password.dll (ProtectKit.NET
assembly)
2. ProFunc64.dll(the ProtectKit.NET password protection function
DLL). For added protection, it is recommended that you rename this
file.
3. ProInfo64.dll (the file where protection information is stored).
For added protection, it is recommended that you rename this file.
To rename the ProInfo64.dll file, use the Set Password Protection
tool (ProtectKit.NET) and choose the "Save As" option,
4. DdScm64.exe.The DdScm64.exe must be registered. For details
about registering DdScm64.exe, see Options for DdScm.
When the above files are deployed, they must be copied to the
same folder. You cannot run a protected application on FD or
DVD(CD)-ROM, remote network drive, etc. The ProtectKit will only
run on local hard disk. It will not run on the drive's root
directory. Also, please avoid copying to certain folders that,
depending on Windows user permissions, do not have write permission
like Windows System folder.
Although the ProtectKit.NET assembly is strong named, do not
register it in the Global Assembly Cache (GAC).
The files that you should deploy also depend on the target platform of your application. For more information about how to deploy your protected application with build options AnyCPU, x86, and x64, please refer to Target Platform
Files That Cannot Be Distributed
The following files cannot be distributed under any
circumstances.
PrNETSetProtect.exe (Set Password Protection Tool) 32/64 bit
Pr3PassGen.exe (Password Generator EXE) 32/64 bit
Pr3PassGen.dll (Password Generator DLL) 32/64 bit
Pr3PassGen.ocx (Password Generator OCX) 32/64 bit