Code First Migrations allows developers to evolve the code-based model so that changes are accurately reflected in the persistent database store. Starting with Oracle Data Access Components (ODAC) 12c Release 3 (12.1.0.2.1), ODP.NET supports Code First and Code First Migrations from Entity Framework 6. No context type was found in the assembly when running code first migration asp.net-mvc entity-framework-6 visual-studio visual. So finaly your code should be like this, Enable-Migrations -ProjectName MyContextProjectNameHere -StartUpProjectName MyStartUpProjectNameHere -Verbose. As you are using visual studio 2017, I assume you might.
![]()
I started a new MVC project with EntityFramework -Version 6.1.2 using Visual Studio 2013 latest update. I made a couple of migrations and updated the database. After this I checked out the project on another computer and opened with Visual Studio 2015 CTP 6.If I go in the package manager console and try to run any migration commands, they're not recognized:add-migrations: The term 'add-migrations' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.How can I manage my migrations using Entity Framework 6 in Visual Studio 2015? I have done a few checks, but I'll recap trying to cover all the ef scenario:ef7 in an asp.net 5 project: the migrations management has been changed and now is handled using the ef migration command.ef7 in a traditional.net application: it's required framework 4.5.1, but at this page you can find a good guide on how to use ef 7 in a traditional app.
It's important to add the EntityFramework.Commands package.ef6: doesn't work with asp.net 5, so even you can install it, the build will be broken. Same situation for most of the actual ef drivers as the ones for mongodb and Postgresql.
If you're not sure is a ef 7 compatible driver, don't install it. At the moment I think you can count just on sqlserver and inMemory.for asp.net 4 applications, the actual installation of the commands is part of the entity framework package itself, so will be installed at the first installation of the package (as rightly pointed out above).In some situations, in an environment where ef package has not been installed, copying an asp.net 4 project and starting to work on it, may give this issue, that magically disappears when for whatever reason the package is installed.
I was having similar issues in that I could not run Add-Migration from the Package Manager Console, either (though I was getting a different error.) Unfortunately, reinstalling EntityFramework was not working for me, perhaps because I had ASP.Net 5 projects in the same solution.
-->
In this tutorial, you start using the EF Core migrations feature for managing data model changes. In later tutorials, you'll add more migrations as you change the data model.
In this tutorial, you:
PrerequisitesAbout migrations
When you develop a new application, your data model changes frequently, and each time the model changes, it gets out of sync with the database. You started these tutorials by configuring the Entity Framework to create the database if it doesn't exist. Then each time you change the data model -- add, remove, or change entity classes or change your DbContext class -- you can delete the database and EF creates a new one that matches the model, and seeds it with test data.
This method of keeping the database in sync with the data model works well until you deploy the application to production. When the application is running in production it's usually storing data that you want to keep, and you don't want to lose everything each time you make a change such as adding a new column. The EF Core Migrations feature solves this problem by enabling EF to update the database schema instead of creating a new database.
To work with migrations, you can use the Package Manager Console (PMC) or the CLI. These tutorials show how to use CLI commands. Information about the PMC is at the end of this tutorial.
Change the connection string
In the appsettings.json file, change the name of the database in the connection string to ContosoUniversity2 or some other name that you haven't used on the computer you're using.
This change sets up the project so that the first migration will create a new database. This isn't required to get started with migrations, but you'll see later why it's a good idea.
Note
As an alternative to changing the database name, you can delete the database. Use SQL Server Object Explorer (SSOX) or the
database drop CLI command:
The following section explains how to run CLI commands.
Create an initial migration
Save your changes and build the project. Then open a command window and navigate to the project folder. Here's a quick way to do that:
Enter the following command in the command window:
You see output like the following in the command window:
Note
If you see an error message No executable found matching command 'dotnet-ef', see this blog post for help troubleshooting.
If you see an error message 'cannot access the file ... ContosoUniversity.dll because it is being used by another process.', find the IIS Express icon in the Windows System Tray, and right-click it, then click ContosoUniversity > Stop Site.
Examine Up and Down methods
When you executed the
migrations add command, EF generated the code that will create the database from scratch. This code is in the Migrations folder, in the file named <timestamp>_InitialCreate.cs. The Up method of the InitialCreate class creates the database tables that correspond to the data model entity sets, and the Down method deletes them, as shown in the following example.
Migrations calls the
Up method to implement the data model changes for a migration. When you enter a command to roll back the update, Migrations calls the Down method.
This code is for the initial migration that was created when you entered the
migrations add InitialCreate command. The migration name parameter ('InitialCreate' in the example) is used for the file name and can be whatever you want. It's best to choose a word or phrase that summarizes what is being done in the migration. For example, you might name a later migration 'AddDepartmentTable'.
If you created the initial migration when the database already exists, the database creation code is generated but it doesn't have to run because the database already matches the data model. When you deploy the app to another environment where the database doesn't exist yet, this code will run to create your database, so it's a good idea to test it first. That's why you changed the name of the database in the connection string earlier -- so that migrations can create a new one from scratch.
The data model snapshot
Migrations creates a snapshot of the current database schema in Migrations/SchoolContextModelSnapshot.cs. When you add a migration, EF determines what changed by comparing the data model to the snapshot file.
Use the dotnet ef migrations remove command to remove a migration.
dotnet ef migrations remove deletes the migration and ensures the snapshot is correctly reset. If dotnet ef migrations remove fails, use dotnet ef migrations remove -v to get more information on the failure.
![]()
See EF Core Migrations in Team Environments for more information about how the snapshot file is used.
Apply the migration
In the command window, enter the following command to create the database and tables in it.
The output from the command is similar to the
migrations add command, except that you see logs for the SQL commands that set up the database. Most of the logs are omitted in the following sample output. If you prefer not to see this level of detail in log messages, you can change the log level in the appsettings.Development.json file. For more information, see Logging in .NET Core and ASP.NET Core.
Use SQL Server Object Explorer to inspect the database as you did in the first tutorial. You'll notice the addition of an __EFMigrationsHistory table that keeps track of which migrations have been applied to the database. View the data in that table and you'll see one row for the first migration. (The last log in the preceding CLI output example shows the INSERT statement that creates this row.)
Run the application to verify that everything still works the same as before.
Compare CLI and PMC
The EF tooling for managing migrations is available from .NET Core CLI commands or from PowerShell cmdlets in the Visual Studio Package Manager Console (PMC) window. This tutorial shows how to use the CLI, but you can use the PMC if you prefer.
The EF commands for the PMC commands are in the Microsoft.EntityFrameworkCore.Tools package. This package is included in the Microsoft.AspNetCore.App metapackage, so you don't need to add a package reference if your app has a package reference for
Microsoft.AspNetCore.App .
Important: This isn't the same package as the one you install for the CLI by editing the .csproj file. The name of this one ends in
Tools , unlike the CLI package name which ends in Tools.DotNet .
For more information about the CLI commands, see .NET Core CLI.
![]()
For more information about the PMC commands, see Package Manager Console (Visual Studio).
Get the codeNext step
In this tutorial, you:
Advance to the next tutorial to begin looking at more advanced topics about expanding the data model. Along the way you'll create and apply additional migrations.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |