EldoS
 Table of Contents >  Deployment
Navigation
Web site
Support
Table Of Contents

Deployment (Application Edition)

  • Windows and Windows Mobile

    With Windows and Windows Mobile depoyment method depends on whether you link SolFS statically or dynamically. SolFS is shipped as static and dynamic library for Visual C++ and eMbedded Visual C++. VCL units for Delphi and C++Builder link SolFS statically. To deploy SolFS in case of dynamic linkage, just copy SolFS.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.

  • .NET

    .NET assemblies are shipped in two forms - in managed code and with Native Link (managed code uses native SolFS.dll for better performance).

    Native Link assemblies must be deployed by copying SolFS.dll and SolFSNet.dll from "<SolFS>\.NET\NativeLink" folder together with your application files.

    Managed code assemblies must be deployed by copying SolFSNet.dll from "<SolFS>\.NET\Managed" folder together with your application files.

    .NET 4.0 assemblies require Visual C++ Multithreaded Runtime DLL (msvcr100.dll). The DLLs are located in "<Microsoft Visual Studio 10.0\VC\redist\x86\Microsoft.VC100.CRT", "<Microsoft Visual Studio 10.0\VC\redist\x64\Microsoft.VC100.CRT" and "<Microsoft Visual Studio 10.0\VC\redist\ia64\Microsoft.VC100.CRT" folders.

    .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" and "<Microsoft Visual Studio 2005>\VC\redist\AMD64\Microsoft.VC80.CRT" folders.

    .NET 1.1 assemblies require Visual C++ Multithreaded Runtime DLL (MSVCR71.dll). You can rely on this DLLs 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.

    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.


  • Android

    You need to include eldos.solfs.jar and libjnisolfs.so as part of your application. Next, deploy libjnisolfs.so together with your application files to the device.

  • Linux, FreeBSD, MacOS X, iOS 4

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

    Static library is linked directly to the application. It doesn't require dynamic library to work and no specific deployment is required.
    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.


Got questions or comments about this topic? Tell us about them.
Contact Us | Terms of Use | Trademarks | Privacy Statement
Copyright (c) 1998-2010, EldoS Corporation