Add-Migration : Exception calling "AddFromFile" with "1" argument(s): "'basePath' cannot be an empty string ("")

Entity Framework Core Add-Migration cannot execute

I had to install the ...Microsoft.EntityFrameworkCore.Design... package in not only the class library that implemented the ...DbContext... class, but also in the project (in this case the GUI/WinForms project) that referenced said class library. This was despite having selected the class library in the Package Manager Console as user Derek suggeste...

EF Migrations: The parameter 'frameworkName' cannot be an empty string

Select proper Startup Project in your solution : Right-click on your project in the solution explorer, select "Set as startup project"

add-migration : Cannot bind argument to parameter 'Path' because it is an empty string

It would be interesting to know with which version of Entity Framework this error occurred. I had the same error with EF 6.3.0 and I am not using docker at all....The solution for me was to go back to version 6.2.0 and create the migration with it.

The string argument 'migrationId' cannot be empty

I finally resolved the issue thanks to @DavidG putting me on the right direction so thank you very much....I realised that when I was checking the installed SDK's on my PC, I noticed that I've installed a pre-release of Dotnet 2.0.0 (I honestly can't remember doing this). Checking the Dotnet version (...dotnet --version...) from PMC confirmed VS wa...

Entity Framework Core 2.0 Add-Migration doesn't create any migration files

There is an issue within the .NET Core class libraries. The successful workaround is to put the following in the csproj file of the ...Model... project:...<PropertyGroup> <GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles> </PropertyGroup>

Add-Migration EntityFramework Core 2.0 trying to select from table in an empty database

For those who are interested: ...https://github.com/aspnet/EntityFrameworkCore/issues/9625

Does EF Core migrations call Startup.Configure() on add-migration

Startup.Configure()... should only contain code to configure the request pipeline. Any app startup/initialization code should go in ...Program.Main()....

Enable-Migrations gives Exception calling "SetData" with "2" argument(s) error

Reading ...this SO post... suggested that maybe some project types may not be compatible with EF 6 migrations. So, instead of using a class library project type of ".NET standard" for the DataAccess project, I tried using the ".NET framework" project type for the DataAccess class library project (where the DbContext is defined). Migrations worked f...

Add-Migration with seeds throwing "no value provided" exception

You are falling into typical ...params object[]... trap....The ...HasData... method has 2 overloads - one with ...params object[] data... and one with ...IEnumerable<object> data.... Due to the reflection call, the type of your ...data... variable is ...object.... Hence you are calling the first overload with ...single... item ...object[]... contai...

C# Problem with DbContext: Argument 1: cannot convert 'string' to 'Microsoft.EntityFrameworkCore.DbContextOptions'

The constructor for Entity Framework Core does not take a single string as a parameter, it takes a ...DbContextOptions... instance. See ...the documentation here.... The constructor you are currently trying to use is the EF6 constructor which does take just the connection string as the parameter (...see here...). The code you have commented out in ...