INSTALLATION INSTRUCTIONS

Normally LLCryptoLib should not be "installed": the only thing to do is to copy the LLCryptoLib.dll in the project directory and then reference it - see examples in the Tutorials directory.

The following instructions are OPTIONAL and almost always not necessary. Follow them only if you need to compile an Unmanaged-COM project or if you know what you are doing.

1. Installing and Registering the Assembly
In order to execute methods from LLCryptoLib assembly you need at least MS .NET Framework v.2.0.xxxx. The framework can be downloaded via Windows Update service.
The library is fully compatible with .NET Framework v.3.0, v.3.5 and v.4.0.

The assembly can be referenced in actual project by just specifying its path as a reference in your development environment. 

[Optional]
If the library needs to be installed in the global assembly cache (GAC) (for instance to be used from COM components, or to be available in .NET development environments such as Visual Studio .NET), you can install the assembly in the global assembly cache using gacutil.exe utility. Assemblies can be uninstalled using the /u option. 

	gacutil /i LLCryptoLib.dll 

If the assembly is to be used privately by a single application, it can be copied directly to the application directory (rather than installing the assembly in the GAC). Private assemblies do not require shared names, but they must be registered for use from COM. 
You can register an assembly using regasm.exe utility. Assemblies can be uninstalled using the /u option. 

	regasm LLCryptoLib.dll 

2. Writing and Compiling Unmanaged Code (COM)
Once the assembly is registered and properly installed, the types defined within the assembly can be used from COM as though they were normal COM types. For example, new objects can be created by calling CoCreateInstance API or by calling CreateObject or GetObject from Visual Basic or script languages. 

3. Generating a Type Library (.NET Server callable by COM clients)
Most unmanaged application development tools require a type library before you can make references to external types. A type library can be generated from LLCryptoLib assembly using the tlbexp.exe, which produces a .tlb file that can then be referenced from your unmanaged development tool. 

	tlbexp LLCryptoLib.dll 

For example, with Visual Basic 6.0, you can reference the .tlb file from the Project/References dialog. In Visual C++ 6.0, you can use the #import statement to import the type defintions from the type library directly into C++. Once the reference to the type library is added to the project, the types defined within that library can be referenced from unmanaged code.


