dotConnect for SQLite Documentation
Deployment
support@devart.com

To deploy applications written with dotConnect for SQLite you should register run-time assemblies Devart.Data.SQLite.dll and Devart.Data.dll at Global Assembly Cache (GAC) for appropriate framework or place them in the folder of your application (Bin folder for web projects). These two assemblies should be available in all applications written with dotConnect for SQLite. Make sure that your project contains the license resource as it is described in Licensing.

Your application should also have access to the sqlite3.dll library. This library can be located either in the application folder or in a system-wide accessible folder. The bitness (32-bit or 64-bit) of the library must correspond to the bitness of your application. If you need your application to use a specific sqlite3.dll library, you can ensure it in the following way: in a folder with your application create a folder named "x86" (without quotes) or "x64" (without quotes) depending on the bitness of your application. Then place the sqlite3.dll library of the corresponding bitness to this folder. This is the first place where dotConnect for SQLite will search for the library.

Another way to install the needed *.dll is to launch the dotConnect for SQLite setup program and choose "Minimal installation". Note that according to End-User License Agreement this is the only install you can do on target machine. You must not distribute any other part of dotConnect for SQLite.

Applications written with dotConnect for SQLite may not contain the license resource when they are deployed on the target machine where dotConnect for SQLite is installed with "Minimal" option.

When your code uses dotConnect for SQLite via a factory-based class, you should register configuration information in the DbProviderFactories section of the *.config file to inform your environment about the existence of the provider factory. The provider factory is described either in machine.config (globally), in app.config or in web.config (just for your application). This is done as follows:

<system.data>
  <DbProviderFactories>
    <remove invariant="Devart.Data.SQLite" />
    <add name="dotConnect for SQLite" invariant="Devart.Data.SQLite" description="Devart dotConnect for SQLite" type="Devart.Data.SQLite.SQLiteProviderFactory, Devart.Data.SQLite, Version=5.1.26.0, Culture=neutral, PublicKeyToken=09af7300eec23701" />
  </DbProviderFactories>
</system.data>

Replace 5.1.26.0 here with your actual version.


ASP.NET Applications

When deploying ASP.NET applications, the following additional assemblies may be needed:

When deploying ASP.NET applications using dotConnect for SQLite SimpleMembership providers, you need to deploy the Devart.Data.SQLite.Web.dll assembly for .NET Framework 4, not the one for .NET Framework 2.0. It is located in the Web\ASP.NET 4 subdirectory of the dotConnect for SQLite installation directory (by default, from Program Files\Devart\dotConnect\SQLite\Web\ASP.NET 4) and has the revision number 4 in its version.

When deploying ASP.NET applications using ADO.NET implementation of ASP.NET Identity via dotConnect for SQLite, you need to deploy the Devart.Data.SQLite.Web.Identity.dll assembly.

When deploying ASP.NET applications using Entity Framework implementation of ASP.NET Identity via dotConnect for SQLite, you need to deploy the Devart.Data.SQLite.Entity.EF6.dll assembly. It is located in the Entity\EF6 subfolder of the dotConnect for SQLite installation folder.

Required Permissions

When dotConnect for SQLite application is used in partially trusted code (this is actual for web projects), it requires medium trust level.

Since dotConnect for SQLite uses standard Microsoft .NET licensing licensing, it additionally requires RegistryPermission. And though SecurityPermission is granted by default when using medium trust level, the set of flags for the SecurityPermission must be extended. You need to add the following flags: Assertion, SkipVerification, UnmanagedCode, and SerializationFormatter.

For the information on how to do this see Configuring Trust Level for Web Applications.

Entity Framework and LightSwitch Projects

When deploying Entity Framework (or LightSwitch) projects, it is necessary to:

  1. First, you need to check if the Devart.Data.SQLite.Entity.EF<Version>.dll assembly is available for your application. The <Version> here is the version of Entity Framework used in your application. For Entity Framework v1 the assembly is called Devart.Data.SQLite.Entity.EF1.dll, for Entity Framework v4 and v5 it is Devart.Data.SQLite.Entity.EF4.dll, for Entity Framework v6 it is Devart.Data.SQLite.Entity.EF6.dll. For Entity Framework Core it is Devart.Data.SQLite.Entity.EFCore.dll. The assembly should reside in the application's folder or in GAC.

    Please note that there are three versions of Devart.Data.SQLite.Entity.EFCore.dll assemblies for Full .NET Framework - for different Entity Framework Core versions - 1.1, 2.2, and 3.1. They are located respectively in \Entity\EFCore, \Entity\EFCore2, and \Entity\EFCore3 subfolders of the dotConnect for SQLite installation folder.

    dotConnect for SQLite .NET Standard compatible assemblies for Entity Framework Core are available via NuGet packages, except the Devart.Data.SQLite.Entity.EFCore.dll for Entity Framework Core 2. The latter can be found in the \Entity\EFCore2\netstandard2.0 subfolder of the dotConnect for SQLite installation folder.

  2. If you use Code-First Migrations feature of Entity Framework v4 or Entity Framework v5, you also need to check if the Devart.Data.SQLite.Entity.Migrations.EF4.dll assembly is available for your application. For Entity Framework v6 this assembly is not needed.
  3. If you use Entity Framework Core Spatials and NetTopologySuite for Entity Framework Core 3, you need to check if the Devart.Data.SQLite.Entity.EFCore3.NetTopologySuite.dll assembly is available for your application. It is located in the \Entity\EFCore3 subfolders of the dotConnect for SQLite installation folder. Additionally, you need to deploy the NetTopologySuite.dll assempbly from the NetTopologySuite 2.1.0 nuget package.
  4. dotConnect for SQLite uses SpatiaLite SQLite extension for working with Entity Framework Core Spatials. So if you use them, you additionally need to deploy the following libraries of this extension, which you can get from the mod_spatialite NuGet package of version 4.3.0.1:

    • libfreexl-1.dll
    • libgcc_s_seh-1.dll
    • libgeos.dll
    • libgeos_c.dll
    • libiconv-2.dll
    • liblzma-5.dll
    • libproj-13.dll
    • libstdc++-6.dll
    • libwinpthread-1.dll
    • libxml2-2.dll
    • mod_spatialite.dll
    • zlib1.dll

    Additionally, you need to deploy the NetTopologySuite.IO.SpatiaLite.dll assembly from the NetTopologySuite.IO.SpatiaLite NuGet package of version 2.0.0.

  5. Inform your environment about the provider factory existence (add the entry to the DbProviderFactories section as it is described above).

You can find these assemblies in the Entity folder in the provider installation folder, in the subforder, corresponding to the Entity Framework version necessary.

If you are registering the provider in the machine.config file, please take into account the Entity Framework version. Entity Framework v1 - specific applications require an entry in the .NET Framework 2.0 configuration file, and Entity Framework v4 and later - specific applications should be registered in the .NET Framework 4.0 configuration file. For Entity Framework Core there is no need to register the provider in the machine.config file.

You can also read Microsoft's Deployment Considerations on ADO.NET Entity Framework.

Deploying LightSwitch applications is described here.

LinqConnect Projects

To deploy applications written with LinqConnect support in dotConnect for SQLite, besides deploying the general assemblies you should register run-time LinqConnect assemblies Devart.Data.SQLite.Linq.dll and Devart.Data.Linq.dll at Global Assembly Cache (GAC) or place them in the folder of your application (the Bin folder for web projects).