Deployment instructions
Drivers
The driver to be deployed is cbfs.sys. Note, that the drivers are different for Win32 and for x64 (AMD 64-bit architecture) platforms.
Debug driver is located in "<CBFS>\Drivers\Debug\32bit" or "<CBFS>\Drivers\Debug\64bit" folders (for Win32 and Win64 platforms).
Release driver is located in "<CBFS>\Drivers\Release\32bit" or "<CBFS>\Drivers\Release\64bit" folders (for Win32 and Win64 platforms).
64-bit version of the driver is available for x64 (AMD64) processor architecture used by most modern 64-bit processors and IA64 (Itanium) processor architecture used by some Intel-produced server processors.
Installation of the drivers to the target system is described here.
User-mode API
Callback File System user-mode API is shipped as .NET assemblies, static library for Visual C++ and VCL units.
- .NET API:
When deploying the project, copy the CBFSNet.dll below to your application folder. Questions about when and how to install the assemblies to Global Assembly Cache are discussed in Working with Assemblies and the Global Assembly Cache and How to: Install an Assembly into the Global Assembly Cache articles.
.NET 2.0 assemblies require Visual C++ Multithreaded Runtime DLLs (msvcm80.dll and msvcr80.dll). You can rely on those DLLs to be present on destination systems, but it's a good idea to include them into the distribution. The DLLs are located in "<Microsoft Visual Studio 2005>\VC\redist\x86\Microsoft.VC80.CRT" folder.
.NET 2.0 assemblies are different for 32-bit and 64-bit platforms. 64-bit .NET 2.0 assemblies are available for x64 (AMD64) processor architecture used by most modern 64-bit processors and IA64 (Itanium) processor architecture used by some Intel-produced server processors.
.NET 1.1 assembly requires Visual C++ Multithreaded Runtime DLL (MSVCR71.dll). You can rely on this DLL to be present on destination systems, but it's a good idea to include it into the distribution. The DLL is located in "<Microsoft Visual Studio 2003>\SDK\v1.1\Bin\" folder. .NET 1.1 assembly can be used only with 32-bit applications.
- C++ API:
C++ class links Callback File System API statically so no deployment is required.
- VCL API:
VCL unit for Delphi and C++Builder links Callback File System API statically so no deployment is required.
Helper DLLs
Helper DLLs can be installed and uninstalled during deployment or deinstallation using the functions exported by Installer DLL that is included within Callback File System package. This DLL can be freely distributed with your projects as long as it is used with the licensed version of Callback File System.
To install or uninstall the helper DLLs from your main application use the calls in Callback File System API: InstallHelperDLL and UninstallHelperDLL.
