I am using Visual Studio 2022 and .NET Core, and I am attempting to develop an EF Core Code First project using MySQL. However, when I try to add an initial migration from the command line by issuing the following command:

dotnet ef migrations add InitialMigration
 I was getting error saying "No project was found. Change the current working directory or use the --project option". So in this post we are going to discuess about that error.

Encountering the error "EF Core Error - No project was found. Change the current working directory or use the --project option" can be frustrating, but there's a straightforward solution.

Here's how we can resolve it:

  1. Firstly, ensure that you are operating in the correct working directory. Sometimes, the error can occur if the current working directory is not set to the project directory containing the Entity Framework Core files.
  2. Alternatively, you can use the --project option to explicitly specify the project directory. This ensures that EF Core knows where to look for the project files.

Here's an example of how we can use the --project option:

dotnet ef migrations add DbMigration --project ProjectDirectory

By ensuring that EF Core knows where to find the project files, we can successfully resolve the error and continue working with migrations in Entity Framework Core.


We encountered the same issue where the provided solutions didn't resolve the problem. In our research, we found a workaround that worked for us:

Instead of using the Package Manager Console, we opted to use the command line in the same folder. When we ran the 'dotnet' command, it provided a helpful error message 

No database provider has been configured for this DbContext. A provider can be configured by overriding the DbContext.OnConfiguring method or by using AddDbContext on the application service provider. If AddDbContext is used, then also ensure that your DbContext type accepts a DbContextOptions<TContext> object in its constructor and passes it to the base constructor for DbContext.

By using the command line instead of the Package Manager Console, we were able to gain more insight into the underlying issue. The error message provided valuable information about the missing database provider configuration, leading us to the correct solution.


I encountered the same issue when attempting to scaffold an existing MySQL database using the following command:

dotnet ef dbcontext scaffold "Server=sjdj7bdhs.secureserver.net; User ID=Quickpickdealdb; Password=a@1997; Database=Quickpickdealdb" MySql.Data.EntityFrameworkCore -o Models

I realized that the error was caused because i was not in the current project directory. Upon checking the current working directory inside the Package Manager Console, i found that it was incorrect.

In our case, the directory was not aligned with the project:

Meaning we were not in the current project directory. Then after switching directories using cd CalculaorApp, we ensured that we were in the project directory before running the command.

Ensuring that we are in the correct project directory is very importent for executing commands related to Entity Framework Core effectively. 


To resolve the issue, you can follow these steps:

  1. Add NuGet Packages: First, we should add the following NuGet packages to our project:
    • Microsoft.EntityFrameworkCore.Tools
    • Microsoft.EntityFrameworkCore.Design
  2. Edit Project File: Next, we need to right-click our project file, select Edit, and add the following code to the ItemGroup containing PackageReference nodes:
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="5.0.0" />
  3. Open Package Manager Console: We then open the Package Manager Console by navigating to Tools → Nuget Package Manager → Package Manager Console.
  4. Navigate to Project Directory: It's importent to change the directory to where our .csproj file resides, this step ensures that the Entity Framework Core tools know which project to operate on.
  5. Add Migration: Now finally, we type the command dotnet ef migrations add InitialMigration in the Package Manager Console to add the initial migration.

By following these steps, we ensure that our project is properly configured to use Entity Framework Core tools. Adding the necessary NuGet packages and configuring the project file allows us to integrate EF Core migrations into our project.


Sometimes, we need to change the current directory in the console/terminal. For example:

cd E:\MyProjectsList\ZymTest\
dotnet ef migrations add InitialMigration

We should also ensure that our package versions are aligned. Changing the current directory in the console/terminal helps ensure that we're working within the correct project directory, avoiding errors related to project location.

Aligning our package versions is importent for maintaining compatibility and stability within our project. Using either all preview1 or all preview2 packages helps prevent conflicts and ensures smooth integration of dependencies.