mirror of https://github.com/abpframework/abp
				
				
				
			
			You can not select more than 25 topics
			Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
		
		
		
		
		
			
		
			
				
					
					
						
							41 lines
						
					
					
						
							2.8 KiB
						
					
					
				
			
		
		
	
	
							41 lines
						
					
					
						
							2.8 KiB
						
					
					
				| # Switch to EF Core SQLite Provider
 | |
| 
 | |
| This document explains how to switch to the **SQLite** database provider for **[the application startup template](Startup-Templates/Application.md)** which comes with SQL Server provider pre-configured.
 | |
| 
 | |
| ## Replace the Volo.Abp.EntityFrameworkCore.SqlServer Package
 | |
| 
 | |
| `.EntityFrameworkCore` project in the solution depends on the [Volo.Abp.EntityFrameworkCore.SqlServer](https://www.nuget.org/packages/Volo.Abp.EntityFrameworkCore.SqlServer) NuGet package. Remove this package and add the same version of the [Volo.Abp.EntityFrameworkCore.Sqlite](https://www.nuget.org/packages/Volo.Abp.EntityFrameworkCore.Sqlite) package.
 | |
| 
 | |
| ## Replace the Module Dependency
 | |
| 
 | |
| Find ***YourProjectName*EntityFrameworkCoreModule** class inside the `.EntityFrameworkCore` project, remove `typeof(AbpEntityFrameworkCoreSqlServerModule)` from the `DependsOn` attribute, add `typeof(AbpEntityFrameworkCoreSqliteModule)` (also replace `using Volo.Abp.EntityFrameworkCore.SqlServer;` with `using Volo.Abp.EntityFrameworkCore.Sqlite;`).
 | |
| 
 | |
| ## UseSqlite()
 | |
| 
 | |
| Find `UseSqlServer()` calls in your solution, replace with `UseSqlite()`. Check the following files:
 | |
| 
 | |
| * *YourProjectName*EntityFrameworkCoreModule.cs inside the `.EntityFrameworkCore` project.
 | |
| * *YourProjectName*MigrationsDbContextFactory.cs inside the `.EntityFrameworkCore.DbMigrations` project.
 | |
| 
 | |
| > Depending on your solution structure, you may find more code files need to be changed.
 | |
| 
 | |
| ## Change the Connection Strings
 | |
| 
 | |
| SQLite 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]( https://www.connectionstrings.com/sqlite/ ) for details of SQLite connection string options.
 | |
| 
 | |
| You typically will change the `appsettings.json` inside the `.DbMigrator` and `.Web` projects, but it depends on your solution structure.
 | |
| 
 | |
| ## Re-Generate the Migrations
 | |
| 
 | |
| The startup template uses [Entity Framework Core's Code First Migrations](https://docs.microsoft.com/en-us/ef/core/managing-schemas/migrations/). EF Core Migrations depend on the selected DBMS provider. So, changing the DBMS provider will cause the migration fails.
 | |
| 
 | |
| * Delete the Migrations folder under the `.EntityFrameworkCore.DbMigrations` project and re-build the solution.
 | |
| * 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 `.DbMigrator` project to create the database and seed the initial data.
 | |
| 
 | |
| ## Run the Application
 | |
| 
 | |
| It is ready. Just run the application and enjoy coding. |