From cb79e6927a01917ddc4c15bb069b21ae04358e2b Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Tue, 3 Apr 2018 16:08:33 -0700 Subject: [PATCH] fix typo --- aspnetcore/data/ef-rp/migrations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/data/ef-rp/migrations.md b/aspnetcore/data/ef-rp/migrations.md index 5b7eb8d189e2..36ff80e658bc 100644 --- a/aspnetcore/data/ef-rp/migrations.md +++ b/aspnetcore/data/ef-rp/migrations.md @@ -181,7 +181,7 @@ Use **SQL Server Object Explorer** to inspect the DB. Notice the addition of an Run the app and verify that everything works. -## Appling migrations in production +## Applying migrations in production We recommend production apps should **not** call [Database.Migrate](https://docs.microsoft.com/dotnet/api/microsoft.entityframeworkcore.relationaldatabasefacadeextensions.migrate?view=efcore-2.0#Microsoft_EntityFrameworkCore_RelationalDatabaseFacadeExtensions_Migrate_Microsoft_EntityFrameworkCore_Infrastructure_DatabaseFacade_) at application startup. `Migrate` shouldn't be called from an app in server farm. For example, if the app has been cloud deployed with scale-out (multiple instances of the app are running).