diff --git a/src/EntityFramework.SqlServer/project.json b/src/EntityFramework.SqlServer/project.json
index 0ef46702627..b60e61e1ffa 100644
--- a/src/EntityFramework.SqlServer/project.json
+++ b/src/EntityFramework.SqlServer/project.json
@@ -1,6 +1,6 @@
{
"version": "7.0.0-*",
- "description": "SQLite data store for Entity Framework.",
+ "description": "Microsoft SQL Server data store for Entity Framework.",
"compilationOptions": {
"warningsAsErrors": true
},
diff --git a/src/Microsoft.AspNet.Diagnostics.Entity/Properties/Strings.Designer.cs b/src/Microsoft.AspNet.Diagnostics.Entity/Properties/Strings.Designer.cs
index de24ff8717d..7f3ef127e19 100644
--- a/src/Microsoft.AspNet.Diagnostics.Entity/Properties/Strings.Designer.cs
+++ b/src/Microsoft.AspNet.Diagnostics.Entity/Properties/Strings.Designer.cs
@@ -154,6 +154,22 @@ internal static string FormatDatabaseErrorPage_ApplyMigrationsFailed()
return GetString("DatabaseErrorPage_ApplyMigrationsFailed");
}
+ ///
+ /// To use migrations from a command prompt you will need to install K Version Manager (KVM). Once installed, you can run migration commands from a standard command prompt in the project directory.
+ ///
+ internal static string DatabaseErrorPage_EnableMigrationsCommandsInfo
+ {
+ get { return GetString("DatabaseErrorPage_EnableMigrationsCommandsInfo"); }
+ }
+
+ ///
+ /// To use migrations from a command prompt you will need to install K Version Manager (KVM). Once installed, you can run migration commands from a standard command prompt in the project directory.
+ ///
+ internal static string FormatDatabaseErrorPage_EnableMigrationsCommandsInfo()
+ {
+ return GetString("DatabaseErrorPage_EnableMigrationsCommandsInfo");
+ }
+
///
/// You can also apply migrations from the command line
///
@@ -282,6 +298,22 @@ internal static string FormatDatabaseErrorPage_PendingMigrationsTitle(object p0)
return string.Format(CultureInfo.CurrentCulture, GetString("DatabaseErrorPage_PendingMigrationsTitle"), p0);
}
+ ///
+ /// A database operartion failed while processing the request.
+ ///
+ internal static string DatabaseErrorPage_Title
+ {
+ get { return GetString("DatabaseErrorPage_Title"); }
+ }
+
+ ///
+ /// A database operartion failed while processing the request.
+ ///
+ internal static string FormatDatabaseErrorPage_Title()
+ {
+ return GetString("DatabaseErrorPage_Title");
+ }
+
///
/// > k ef migration apply
///
diff --git a/src/Microsoft.AspNet.Diagnostics.Entity/Properties/Strings.resx b/src/Microsoft.AspNet.Diagnostics.Entity/Properties/Strings.resx
index c034438b09f..12b4868cf52 100644
--- a/src/Microsoft.AspNet.Diagnostics.Entity/Properties/Strings.resx
+++ b/src/Microsoft.AspNet.Diagnostics.Entity/Properties/Strings.resx
@@ -127,7 +127,7 @@
The context type '{0}' was not found in services. This usually means the context was not registered in services during startup. You probably want to call AddScoped<{0}>() inside the UseServices(...) call in your application startup code. Skipping display of the database error page.
- An exception occured while calculating the database error page content. Skipping display of the database error page.
+ An exception occurred while calculating the database error page content. Skipping display of the database error page.> k ef migration add [migration name]
@@ -142,22 +142,22 @@
Applying Migrations...
- An error occured applying migrations, try applying them from the command line
+ An error occurred applying migrations, try applying them from the command line
- You can also apply migrations from the command line
+ You can also apply migrations from the command line:Try refreshing the page
- From the command line, scaffold a new migration and apply it to the database
+ From the command line, scaffold a new migration and apply it to the database:Use migrations to create the database for {0}
- Scaffold a new migration for these changes and apply them to the database from the command line
+ Scaffold a new migration for these changes and apply them to the database from the command line:There are pending model changes for {0}
@@ -184,7 +184,7 @@
The context type '{0}' was not found in services. This usually means the context was not registered in services during startup. You probably want to call AddScoped<{0}>() inside the UseServices(...) call in your application startup code.
- An error occured while applying the migrations for '{0}'. See InnerException for details.
+ An error occurred while applying the migrations for '{0}'. See InnerException for details.The context type '{0}' could not be loaded. Ensure this is the correct type name for the context you are trying to apply migrations for.
@@ -195,4 +195,10 @@
Request path matched the path configured for this migrations endpoint ({0}). Attempting to process the migrations request.
+
+ A database operation failed while processing the request.
+
+
+ To use migrations from a command prompt you will need to <a href='http://go.microsoft.com/fwlink/?LinkId=518242'>install K Version Manager (KVM)</a>. Once installed, you can run migration commands from a standard command prompt in the project directory.
+
\ No newline at end of file
diff --git a/src/Microsoft.AspNet.Diagnostics.Entity/Views/DatabaseErrorPage.cs b/src/Microsoft.AspNet.Diagnostics.Entity/Views/DatabaseErrorPage.cs
index 49bf1459da8..2c14bd00113 100644
--- a/src/Microsoft.AspNet.Diagnostics.Entity/Views/DatabaseErrorPage.cs
+++ b/src/Microsoft.AspNet.Diagnostics.Entity/Views/DatabaseErrorPage.cs
@@ -83,8 +83,13 @@ public override async Task ExecuteAsync()
#line default
#line hidden
- WriteLiteral("\r\n \r\n\r\n\r\n
A database operartion failed while proce" +
-"ssing the request.