Deployment

In This Topic

To deploy applications written with dotConnect for SQL Server you should register run-time assemblies Devart.Data.SqlServer.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 SQL Server. Make sure that your project contains the license resource as it is described in Licensing.

Another way to install the needed *.dll is to launch the dotConnect for SQL Server 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 SQL Server.

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

When your code uses dotConnect for SQL Server 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.SqlServer" />
    <add name="dotConnect for SQL Server" invariant="Devart.Data.SqlServer" description="Devart dotConnect for SQL Server" type="Devart.Data.SqlServer.SqlProviderFactory, Devart.Data.SqlServer, Version=2.70.852.0, Culture=neutral, PublicKeyToken=09af7300eec23701" />
  </DbProviderFactories>
</system.data>

Replace 2.70.852.0 here with your actual version.

Continuous Integration

If you set up a pipeline for compiling your source code from repository on a build server periodically or even after every commit, you should add a step to your pipeline for installing the provider on the build server for copying Devart assemblies, and enabling automatic generation of .NET Framework license resource from provider entry in licenses.licx. For example, the corresponding step in Azure DevOps Pipeline can be the following one if you copied the provider installation to the root folder of your repository:

- task: CmdLine@2
  inputs:
    script: '$(Build.SourcesDirectory)\dcsqlserver.exe /TYPE=FULL /VERYSILENT'

More information about the command line installation keys can be found here.

ASP.NET Applications

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

Devart.Data.SqlServer.Web.dll - in case if the SqlDataSource component or ASP.NET providers are used;
App_Licenses.dll - if the application is a non-precompiled web site.

Required Permissions

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

Since dotConnect for SQL Server 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.

[email protected]