Update-Database command is missing in EF Core

Can't update database using EF Migrations after updating to EF 6.0.0-alpha

OK. I have found the solution. It appears that EF expects the Primary Key constraint of ...__MigrationHistory... table to have the name ...PK_dbo.__MigrationHistory.... but it is ...PK___MigrationHistory.......So the following sql statements will do the trick....ALTER TABLE __MigrationHistory drop CONSTRAINT PK___MigrationHistory ALTER TABLE __Migr...

Command line connection string for EF core database update

Keep both connection strings in ...appsettings.json.... Inherit a child context class from the main one and override ...OnConfiguring... with another connection string:...public class ScaffoldContext : MyDbContextName { protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder) { string scaffoldConnStr = Configur...

Asp.Net Core EF Core many to many relation update command

Let's create some sample data ...var p = new Post { ... }; var t = new Tag { ... }; var pt = new PostTag { Post = p, Tag = t }; ...This is still in-memory so we have to add it to the context, starting with:...db.Posts.Add(p); db.Tags.Add(t); ...Note that at this stage neither ...p... nor ...t... has any knowledge of ...pt.... There are two ways to ...

ef core don´t use ASPNETCORE_ENVIRONMENT during update-database

Using the package manager in Visual Studio was a dead end for me. The solution was:...Add below in .csproj in the starter project in solution:...<ItemGroup> <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0" /> </ItemGroup> ...Open the command tool(cmd) and go the the same folder as .csproj for start pr...

EF Core `update-database` on MySql fails with `__EFMigrationsHistory' doesn't exist`

This isn't related to ASP.NET Identity or ASP.NET Core. This is related to Entity Framework in general. When you update a database, EF uses the ...__EFMigrationsHistory... to record which migrations were executed so it doesn't perform them again in the future. ...This functionality is implemented by the ...database provider..., not EF itself. There...

EF Core: Update-Database command not creating user tables

The solution was eventually simple to resolve for me using Visual Studio 2017, using Microsoft.AspNetCore.All 2.0.5.. I wasn't receiving any error messages I just had to change this in my ...appsettings.json.... I had to change "...Server=(localdb)\\mssqllocaldb;..." to this: "...Server=Localhost;...." Then I ran the command, "...Update-Database..

Error: Table 'Table_name' already exists after Update-Database command

By removing your previous migration that creates the table 'Student' EntityFramework now is generating the migration with a Create Table Script, if you want to remove a migration you must revert it from your database aswell. Now you can either recreate your database or revert/delete the 'Students' table on your database.

__EFMigrationsHistory table remains empty though update-database command applied

EF core does not use ...Enable-Migration... any more.You need to use below code if you would like to add migrations:...Add-Migration MigrationName Update-Database ...Refer to ...https://docs.microsoft.com/en-us/ef/core/managing-schemas/migrations/

EF Core Update-Database throws System.NullReferenceException

It seems that it is an issue with Microsoft.Data.Sqlite.Core. I just added a reference Microsoft.Data.Sqlite and everything works right now. ...OBS!!!...There is already an open ticket about this ...GitHub/EF/Issues

CREATE UNIQUE INDEX duplicate key when I update-database by EF Core

You're creating a unique index on the column ...CountryId... with this code:...migrationBuilder.CreateIndex( name: "IX_Cities_CountryId", schema: "dbo", table: "Cities", column: "CountryId", unique: true); ...Since that is not unique I'd suggest setting ...unique... to ...false.... Typo maybe?