Download the Server Trial Edition of CryptoSys API
Download the Server Trial Edition of CryptoSys APIThe Server Trial Edition of CryptoSys API is available at no charge to evaluate the CryptoSys API in all environments including 32-bit IIS/ASP. It has all the functionality of the Developer Edition but it expires after 60 days. Please read the full licence document before downloading.
The latest Server Trial version is 4.4.1.0 dated 9 August 2010.
A Developer's Licence for CryptoSys API allows full incorporation into your applications for distribution to third parties world wide, or for site-wide use within your organisation in all environments. Buy Now!. The Developer Edition works on all advertised platforms and replaces both the Personal and Server Trial editions.
Download the Server Trial Edition of the CryptoSys API now:
The Server Trial Edition includes the manual and test functions in Visual Basic, C, VB.NET, C# and ASP. It also includes the source code for the 32-bit ActiveX interface. Please read the licence conditions for the Server Trial Edition.
This build includes an alternative core DLL compiled for 64-bit machines. It should install both the 32-bit and 64-bit core DLLs in the correct Windows system folders. Windows will automatically select the correct DLL for the platform of the application you are running. For more information see using on a 64-bit system. Note that the 32-bit ActiveX/COM interface is not supported by 64-bit Microsoft Office.
The Server Trial Edition will fail silently if not installed properly or expired. It does, however, write error messages to the Event Viewer (Administrative Tools > Event Viewer > Application log).
The default installation procedure for the Server Trial Edition makes a registry setting that turns off the MessageBox warning if there is a critical error (including the licence expiring). This is recommended for use on an IIS server. There will still be an error event that can be checked using the Event Viewer in the Application Log. If you want to change this setting, use one of these two registry editor files. You will need administrator privileges.
For more details refer to the section Optional Registry Settings in the manual.
This page last updated 10 August 2009
