The AspEncrypt component consists of a single file, aspencrypt.dll (or, in case of the 64-bit version, aspencrypt64.dll).
Being a COM object, this DLL needs to be registered on the server. The installer aspencrypt.exe (aspencrypt64.exe)
performs the registration automatically. If manual installation is needed, the DLL must be registered
with regsvr32.
To use AspEncrypt under .NET, the interop assembly ASPENCRYPTLib.dll (shipped with the component) needs to be placed in the
/Bin subfolder of the application. The main DLL aspencrypt.dll still needs to be properly registered.
AspEncrypt works for 30 days without a registration key, and throws an expiration error afterwards.
The purchased key needs to be placed in the system registry, as the default value, under
HKEY_LOCAL_MACHINE\Software\Persits Software\AspEncrypt\RegKey
If the 32-bit version of AspEncrypt is run on the 64-bit version of Windows, the key should be placed under
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Persits Software\AspEncrypt\RegKey
Alternatively, the registration key can be specified in your code via the RegKey property of the top-level CryptoManager object, as follows:
Set CM = Server.CreateObject("Persits.CryptoManager")
CM.RegKey = "12345-12345-12345"
...
The current expiration date of the component can be retrieved via the Expires property, as follows:
Set CM = Server.CreateObject("Persits.CryptoManager")
Response.Write CM.Expires
If this property returns 9/9/9999 it means a permanent registration key is being used.
