Error: “Feature is not supported” (license key validation in .NET Standard)

Error: “Feature is not supported” (license key validation in .NET Standard)

This error occurs when Devart .NET Standard assemblies cannot validate a license key at runtime. The guidance applies to all dotConnect providers.

After migrating a working .NET Framework application to .NET Core / .NET 6–9 and referencing NuGet packages, the error appears when opening a database connection.

Unlike the full .NET Framework, .NET Core / .NET 6–9 requires a license key to be provided at runtime. If the key is missing or invalid, .NET Standard assemblies throw: “Feature is not supported.”

Resolution

Provide the license key in the connection string using the License Key parameter:
​
var conn = new Devart.Data.MySql.MySqlConnection();
conn.ConnectionString = "User Id=root;Host=localhost;Database=Test;License Key=YOUR_ACTIVATION_KEY;";
conn.Open();


    • Related Articles

    • Specifying the License Key in the Devart EF Core Model

      This article is for dotConnect providers with ORM support (all except Universal and SQL Server). When creating a Devart EF Core model, the license key is not required at design time. However, during execution the following error may appear: “Feature ...

    • "License key is missing" error in dotConnect products version 11.0+

      Users may encounter the error "License key is missing" after upgrading to dotConnect version 11.0 or later when using .NET Framework projects. In the latest releases of dotConnect for Oracle (starting from 11.0.0), the licensing approach for .NET ...

    • How to Troubleshoot the 'License Not Activated' Error

      If you encounter a "license not activated" error: Check the license status in the driver settings. Try restarting the application or server. Reactivate the license using Devart’s License Manager. For web apps, ensure the license file is accessible to ...

    • SSH Host Key Verification Error in dbForge Studio for MySQL

      Attempting to connect to a server over SSH may fail with the following error message: Can't connect to SSH server: The computed hash verification does not correspond to the received. (code 0) The same connection may work successfully in PuTTY or ...

    • Changing Connections Is Not Supported for Non-Empty Query Documents

      Attempting to change the connection for a query document may result in the following error: "Cannot change the connection for a non-empty query document" As a result, the connection cannot be switched to another server or environment while the ...