text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 The string argument '{argumentName}' cannot be empty. The collection argument '{argumentName}' must contain at least one element. 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 occurred while calculating the database error page content. Skipping display of the database error page. > dotnet ef migrations add [migration name] Apply Migrations Migrations Applied Applying Migrations... An error occurred applying migrations, try applying them from the command line In Visual Studio, you can use the Package Manager Console to apply pending migrations to the database: Try refreshing the page In Visual Studio, use the Package Manager Console to scaffold a new migration and apply it to the database: Use migrations to create the database for {0} In Visual Studio, use the Package Manager Console to scaffold a new migration for these changes and apply them to the database: There are pending model changes for {0} There are migrations for {0} that have not been applied to the database Applying existing migrations for {0} may resolve this issue > dotnet ef database update The value provided for argument '{argumentName}' must be a valid value of enum type '{enumType}'. Migrations successfully applied for context '{0}'. Request is valid, applying migrations for context '{0}'. 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 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. No context type was specified. Ensure the form data from the request includes a contextTypeName value, specifying the context to apply migrations for. 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. {0} occurred, checking if Entity Framework recorded this exception as resulting from a failed database operation. Entity Framework recorded that the current exception was due to a failed database operation. Attempting to show database error page. Entity Framework did not record any exceptions due to failed database operations. This means the current exception is not a failed Entity Framework database operation, or the current exception occurred from a DbContext that was not obtained from request services. The target data store is not a relational database. Skipping the database error page. The current exception (and its inner exceptions) do not match the last exception Entity Framework recorded due to a failed database operation. This means the database operation exception was handled and another exception occurred later in the request. PM> Add-Migration [migration name] PM> Update-Database Alternatively, you can scaffold a new migration and apply it from a command prompt at your project directory: Alternatively, you can scaffold a new migration and apply it from a command prompt at your project directory: Alternatively, you can apply pending migrations from a command prompt at your project directory: