End-User Licensing and Deployment with dotConnect

End-User Licensing and Deployment with dotConnect

Applications developed with dotConnect can be distributed to end users without additional licensing costs. This article describes the licensing rules and deployment requirements. The information applies to all dotConnect providers.

End users of an application created with dotConnect do not require their own Devart license. A single valid license held by the developer is sufficient, and no additional fees are charged for deployment or distribution.

The End-User License Agreement (EULA) permits redistribution of the run-time Devart assemblies, provided that they cannot be reused by any application other than the licensed solution.

Deployment Requirements

For deployment of applications built with dotConnect (for example, dotConnect for MySQL), the following assemblies must be available on the target machine:
  1. Devart.Data.MySql.dll
  2. Devart.Data.dll
These assemblies can be delivered in one of two ways:
  1. Registered in the Global Assembly Cache (GAC) for the corresponding .NET Framework version.
  2. Placed in the application’s directory (for web projects, in the Bin folder).
A full licensed installation of dotConnect is not required on the target system. As an alternative, it is possible to run the provider setup program with the Minimal installation option, which installs only the necessary assemblies. According to the EULA, this is the only permitted installation on end-user machines, and no other components of dotConnect may be redistributed.
    • Related Articles

    • dotConnect for Oracle distribution

      dotConnect for Oracle is distributed in two ways: - As the installer that provides assemblies for Full .NET Framework, documentation, samples, and all the necessary files. - As NuGet packages with .NET Standard compatible assemblies for .NET Core. ...
    • Installation vs. NuGet in dotConnect Providers

      dotConnect providers can be added to a project in two ways: by installing the product or by using NuGet packages. The choice depends on the project type and the .NET version you are targeting. This article applies to all dotConnect providers. Two ...
    • Where to Apply the License Key in dotConnect Providers

      License key usage in dotConnect providers varies depending on the target framework. In .NET Framework projects, licensing is managed automatically during installation, whereas .NET Core and later versions require the license key to be provided at ...
    • Using SSL with dotConnect for PostgreSQL from NuGet

      When using dotConnect for PostgreSQL via NuGet packages, note that SSL support is not included in the NuGet assemblies by default. To enable SSL connections, you must manually add the necessary assemblies from the full Devart installation package to ...
    • Updating dotConnect to a New Version

      This article explains the procedure for updating dotConnect to the latest version. The instructions apply to all dotConnect providers. Update Procedure 1. Uninstall the previous version Open Settings → Apps → Installed apps → Uninstall and remove all ...