Deployment (Standard Edition)

• Windows and PocketPC

  With Windows and PocketPC 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 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 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.