Deployment (Application Edition)

  • .NET (Windows)

    .NET assemblies are offered in one form that does not depend on MS VC Runtime, but requires an unmanaged CBFSStorage.dll instead. The unmanaged DLL, CBFSStorage.dll, is provided next to CBFSStorage2017Net.dll assembly.

    .NET assemblies must be deployed by copying CBFSStorage.dll and CBFSStorage2017Net.dll from "<CBFS Storage>\.NET" folder together with your application files.

    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 Xamarin for Android, iOS, macOS

    Xamarin assemblies contain everything inside. However, different assemblies are provided for deployment to different target platforms.


  • Java (desktops and servers, Android)

    You need to include callbacktech.cbfsstorage.jar and libjnicbfsstorage.so as part of your application. Reference callbacktech.cbfsstorage.jar as the library of your project (compiler will deal with it automatically) and also put libjnicbfsstorage.so to "lib" folder of your APK file. Then, before using CBFS Storage in your Java code, you have to call System.loadLibrary("libjnicbfsstorage");

  • C and C++ on Windows and Windows Mobile

    With Windows and Windows Mobile, the depoyment method depends on whether you link CBFS Storage statically or dynamically.

    To deploy CBFS Storage in the case of dynamic linkage, just copy CBFSStorage.dll together with your application files. No special actions are required on the end-user system. No deployment is needed in case of static linkage.

    CBFS Storage is shipped as the static and dynamic libraries for Visual C++ and eMbedded Visual C++. 32-bit VCL units for Delphi and C++Builder link CBFS Storage statically. 64-bit VCL units require CBFSStorage.dll to be deployed together with your application files.

  • C and C++ on Linux, FreeBSD, macOS, iOS

    The libraries are shipped as a static library and a shared object / dylib (dynamic library).

    The static library is linked directly to the application. It doesn't require dynamic library to work and no specific deployment is required.
    The dynamic library is provided as a file which needs to be deployed together with your application(s). No special actions are needed on the end-user system.