From 9a41f4eb60328c9e6781a825e2f4ad09c6eaf10c Mon Sep 17 00:00:00 2001 From: Stef Heyenrath Date: Wed, 6 Nov 2019 19:11:01 +0100 Subject: [PATCH] =?UTF-8?q?Replace=20all=20double=20quotes=20(=E2=80=9D)?= =?UTF-8?q?=20by=20a=20normal=20double=20quote=20character=20(").?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace all double quotes (”) by a normal double quote character ("). This makes sure that the commands can be copy-pasted into the command prompt. --- .../ef6/modeling/code-first/migrations/migrate-exe.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/entity-framework/ef6/modeling/code-first/migrations/migrate-exe.md b/entity-framework/ef6/modeling/code-first/migrations/migrate-exe.md index bb89184fa1..2ce572103a 100644 --- a/entity-framework/ef6/modeling/code-first/migrations/migrate-exe.md +++ b/entity-framework/ef6/modeling/code-first/migrations/migrate-exe.md @@ -38,7 +38,7 @@ The above will display the help page associated with this utility, note that you ## Migrate to the latest migration ``` console -Migrate.exe MyMvcApplication.dll /startupConfigurationFile=”..\\web.config” +Migrate.exe MyMvcApplication.dll /startupConfigurationFile="..\\web.config" ``` When running migrate.exe the only mandatory parameter is the assembly, which is the assembly that contains the migrations that you are trying to run, but it will use all convention based settings if you do not specify the configuration file. @@ -46,7 +46,7 @@ When running migrate.exe the only mandatory parameter is the assembly, which is ## Migrate to a specific migration ``` console -Migrate.exe MyApp.exe /startupConfigurationFile=”MyApp.exe.config” /targetMigration=”AddTitle” +Migrate.exe MyApp.exe /startupConfigurationFile="MyApp.exe.config" /targetMigration="AddTitle" ``` If you want to run migrations up to a specific migration, then you can specify the name of the migration. This will run all previous migrations as required until getting to the migration specified. @@ -54,7 +54,7 @@ If you want to run migrations up to a specific migration, then you can specify t ## Specify working directory ``` console -Migrate.exe MyApp.exe /startupConfigurationFile=”MyApp.exe.config” /startupDirectory=”c:\\MyApp” +Migrate.exe MyApp.exe /startupConfigurationFile="MyApp.exe.config" /startupDirectory="c:\\MyApp" ``` If you assembly has dependencies or reads files relative to the working directory then you will need to set startupDirectory. @@ -62,7 +62,7 @@ If you assembly has dependencies or reads files relative to the working director ## Specify migration configuration to use ``` console -Migrate.exe MyAssembly CustomConfig /startupConfigurationFile=”..\\web.config” +Migrate.exe MyAssembly CustomConfig /startupConfigurationFile="..\\web.config" ``` If you have multiple migration configuration classes, classes inheriting from DbMigrationConfiguration, then you need to specify which is to be used for this execution. This is specified by providing the optional second parameter without a switch as above. @@ -70,7 +70,7 @@ If you have multiple migration configuration classes, classes inheriting from Db ## Provide connection string ``` console -Migrate.exe BlogDemo.dll /connectionString=”Data Source=localhost;Initial Catalog=BlogDemo;Integrated Security=SSPI” /connectionProviderName=”System.Data.SqlClient” +Migrate.exe BlogDemo.dll /connectionString="Data Source=localhost;Initial Catalog=BlogDemo;Integrated Security=SSPI" /connectionProviderName="System.Data.SqlClient" ``` If you wish to specify a connection string at the command line then you must also provide the provider name. Not specifying the provider name will cause an exception.