Switch to EF Core MySQL Provider

    project in the solution depends on the Volo.Abp.EntityFrameworkCore.SqlServer NuGet package. Remove this package and add the same version of the package.

    Replace the Module Dependency

    Find YourProjectNameEntityFrameworkCoreModule class inside the .EntityFrameworkCore project, remove typeof(AbpEntityFrameworkCoreSqlServerModule) from the DependsOn attribute, add typeof(AbpEntityFrameworkCoreMySQLModule) (also replace using Volo.Abp.EntityFrameworkCore.SqlServer; with using Volo.Abp.EntityFrameworkCore.MySQL;).

    • YourProjectNameEntityFrameworkCoreModule.cs inside the .EntityFrameworkCore project.
    • YourProjectNameMigrationsDbContextFactory.cs inside the .EntityFrameworkCore.DbMigrations project.

    Change the Connection Strings

    MySQL connection strings are different than SQL Server connection strings. So, check all appsettings.json files in your solution and replace the connection strings inside them. See the connectionstrings.com for details of MySQL connection string options.

    The startup template uses . EF Core Migrations depend on the selected DBMS provider. So, changing the DBMS provider will cause the migration fails.

    • Run Add-Migration "Initial" on the Package Manager Console (select the .DbMigrator (or .Web) project as the startup project in the Solution Explorer and select the .EntityFrameworkCore.DbMigrations project as the default project in the Package Manager Console).

    This will create a database migration with all database objects (tables) configured.

    Run the Application

    It is ready. Just run the application and enjoy coding.