protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder) {
  optionsBuilder.UseMySql(@"User Id=root;Host=localhost;Database=Test;");
Protected Overrides Sub OnConfiguring(optionsBuilder As DbContextOptionsBuilder)
	optionsBuilder.UseMySql("User Id=root;Host=localhost;Database=Test;")
End Sub
The mapping supported by Entity Framework Core is described in details in the corresponding section of Entity Framework documentation. If you plan to support several data sources for one base Entity Framework model, that is mapped to tables and columns named differently in different data sources, you can use special provider-specific extension methods in fluent mapping in order to support specific mapping for each data source simultaneously. dotConnect for MySQL provides the following extension methods:
  
ForMySqlToTable() - specifies the table name.
  
ForMySqlHasColumnName() - specifies the column name.
  
ForMySqlHasColumnType() - specifies the column type.
  
ForMySqlHasName() - specifies the the name of the index and primary key.
  
ForMySqlHasConstraintName() - specifies the foreign key.
  
ForMySqlHasDefaultValueSql() - specifies the column default value.
Deploying an Entity Framework Project
When deploying Entity Framework projects, it is necessary to: 
Check if the required assemblies Devat.Data.dll, Devart.Data.MySql.dll, and Devart.Data.MySql.Entity.EF<Version>.dll are 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.MySql.Entity.EF1.dll "1", for Entity Framework v4 it is Devart.Data.MySql.Entity.EF4.dll, for Entity Framework v5 and v6 it is Devart.Data.MySql.Entity.EF5.dll or Devart.Data.MySql.Entity.EF6.dll respectively. For Entity Framework Core it is Devart.Data.MySql.Entity.EFCore.dll. The assembly should reside in the application's folder or in GAC. 
If you use Code-First Migrations feature of Entity Framework v4 or Entity Framework v5, you also need to check if the Devart.Data.MySql.Entity.Migrations.EF<Version>.dll assembly is available for your application. For Entity Framework v6 this assembly is not needed. 
If you use Entity Framework Spatials and NetTopologySuite, you also need to check if the Devart.Data.MySql.Entity.Spatials.EF<Version>.dll assembly is available for your application.
If you use Entity Framework Core Spatials and NetTopologySuite for Entity Framework Core 3, you need to check if the Devart.Data.MySql.Entity.EFCore3.NetTopologySuite.dll assembly is available for your application. It is located in the \Entity\EFCore3 subfolders of the dotConnect for MySQL installation folder. Additionally, you need to deploy the NetTopologySuite.dll assempbly from the NetTopologySuite 2.1.0 nuget package.
For Entity Framework v1 - v6, you need to inform your environment about the provider factory existence (add the entry to the 
DbProviderFactories section as it is described above). 
  <DbProviderFactories>
    <remove invariant="Devart.Data.MySql" />
    <add name="dotConnect for MySQL" invariant="Devart.Data.MySql"
     description="Devart dotConnect for MySQL"
     type="Devart.Data.MySql.MySqlProviderFactory, Devart.Data.MySql,
       Version=8.3.215.0, Culture=neutral, PublicKeyToken=09af7300eec23701" />
  </DbProviderFactories>
</system.data>
Replace 8.3.215.0 here with your actual version.
You can find the necessary assemblies in the Entity folder in the provider installation folder, in the subfolder, 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 Micrsoft's Deployment Considerations
on ADO.NET Entity Framework.
dotConnect for MySQL is compatible
with the latest version of ADO.NET Entity Framework and Visual Studio.
The following MySQL version is required for Entity Framework to function properly:  5.0 or higher (both MySQL and MariaDB).

Migration between ADO.NET Entity Data Model (*.edmx) and Devart Entity Model (*.edml)
To migrate your ADO.NET Entity Data Model to Devart Entity Model, change the extension of the model file to edml (edmx -> edml), set the Build Action property of your model to "DevartEntityDeploy", and Custom Tool to "DevartEfGenerator". After that the model can be edited with the Devart Entity Developer.
To migrate your Devart Entity Model to ADO.NET Entity Data Model, change the model file extension (edml -> edmx),  set the Build Action property of your model to "EntityDeploy", and Custom Tool to "EntityModelCodeGenerator". After that the model can be edited with Entity Designer.
Both *.edml and *.edmx can be opened and edited manually using XML Editor.