CODEWITHSUNDEEP
ef-code-first.net-coreentity-framework-coreentity-framework-migrationsdotnet-cli
Shiva
Shiva

Reputation: 20935

EF Core Error - No project was found. Change the current working directory or use the --project option

I am using Visual Studio 2015 and dotnet core and trying to develop an EF Core Code First project using Sqlite and this documentation / tutorial, which also uses Sqlite => NET Core - New Database

When I try to add an initial migration from the command line ( I am CD-ed into the folder that my data model project is located in) by issuing the following command

dotnet ef migrations add InitialMigration

...I get the following Error.

enter image description here

No project was found. Change the current working directory or use the --project option.

I even tried using the --project option like so.

> dotnet --project "C:\Shiva\EF\EFCFSqlite.Data.xproj"  ef migrations add InitialMigration

but that gives the following error.

Unknown option: --project
.NET Command Line Tools (1.0.0-preview2-003131)
Usage: dotnet [host-options] [command] [arguments] [common-options]

I noticed that the documentation is using .csproj file whereas my Project is showing a xproj file. Also the docs mention something about not using project.json anymore :(

Here's my project.json file. 

{
  "version": "1.0.0-*",

  "dependencies": {
    "Microsoft.EntityFrameworkCore.Sqlite": "1.1.1",
    "Microsoft.EntityFrameworkCore.Sqlite.Design": "1.1.1",
    "NETStandard.Library": "1.6.1"
  },
  "tools": {
    "Microsoft.EntityFrameworkCore.Tools.DotNet":"1.0.0"
  },
  "frameworks": {
    "netstandard1.6": {
      "imports": "dnxcore50"
    }
  }

What has changed? Do we have no choice but to Install Visual Studio 2017 and start from scratch?? Is project.json and all this other stuff no longer honored?

Seems like a massive change to me if that's the case :(

Upvotes: 69

Views: 132845

Answers (14)

Keith Davidson
Keith Davidson

Reputation: 790

You are most likely in the directory that your IDE project is in. You need to change directories to the directory with the actual .Net project in.

In my case, I am using Rider, rather than Visual Studio, and on macOS. So there is an outer MyProject directory containing the Rider project file .idea, and things like .git, and .gitignore. Then there is an inner MyProject/MyProject directory containing all the .Net project stuff such as your source code.

So in my case, it was simply

cd MyProject

Then it worked. It created a Migrations directory containing the migration.

Upvotes: 0

Enes Şağban
Enes Şağban

Reputation: 11

You should be sure current directory on Context file's folder. You can check with use "dir". And that was different, so change directory with using "cd".

Upvotes: 1

thp3loN2
thp3loN2

Reputation: 27

I know this is old but it also helps to check the version of your .net so that your install the required version. Check the accepted answer here: Command dotnet ef not found

Upvotes: 0

sweetnandha cse
sweetnandha cse

Reputation: 981

for mac os i did like this.. working fine for me.

dotnet ef database update -c ApplicationDbContext

Upvotes: -1

Ruslan
Ruslan

Reputation: 171

If you're getting this error while working with the ABP Framework and trying to add new migration:

  • Check that you're executing the command in the EFCore project/folder e.g: C:\Users\rushas\source\repos\MyProject\aspnet-core> for cmd command
  • If you have more than one DbContext, make sure to append context name to your command. Use -Context for PowerShell command and --context for the rest of it. e.g: dotnet ef migrations add InitialMigration --context MyProjectDbContext

Upvotes: 0

Shakir Ahmed
Shakir Ahmed

Reputation: 547

Just simply use this command.

Add-Migration InitialCreated -c bodoContext

No need to worry.

Upvotes: 2

devknight
devknight

Reputation: 43

Add references Microsoft.EntityFrameworkCore.Design and Microsoft.EntityFrameworkCore.Tools

Then run:

dotnet-ef migrations add InitialCreate --project ProjectName

or

dotnet ef migrations add InitialCreate --project ProjectName

Upvotes: -1

Marin
Marin

Reputation: 73

Apparently, it may sound funny, but in my case when I was getting this error I had the server-side of the app running. Basically, make sure that your app is not running at all when trying to create migrations. As I said, for me that was the cure. Might be a bit of advice for those who couldn't fix it by following the marked answer.

Upvotes: 1

TAHA SULTAN TEMURI
TAHA SULTAN TEMURI

Reputation: 5201

It simply Means that

YOU ARE NOT IN CURRENT PROJECT DIRECTORY

I was facing the same issue when scaffolding existing database of MySql using this.

Command I was executing:

dotnet ef dbcontext scaffold "Server=123.1.1.1;Uid=abc;Pwd=abc;Database=myDB;Connection Timeout=20;Persist Security Info=False;Port=3306;Allow User Variables=True;Connect Timeout=120;" MySql.Data.EntityFrameworkCore -o Models

Causing the same error , then I checked current working directory inside package manager console and found incorrect.

In my case

enter image description here

Mean I was not in current project directory then after switching directory

cd SSGCApp

Now you are in project directory all good to run the Command.

Upvotes: 56

QuranX Administrator
QuranX Administrator

Reputation: 425

  1. Add the nuget package Microsoft.EntityFrameworkCore.Tools
  2. Add the nuget package Microsoft.EntityFrameworkCore.Design
  3. Right-click your project file, select Edit and then add the following to the ItemGroup that contains PackageReference nodes

<DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.3" />

(You can find the latest version by finding it in the Nuget Package manager)

  1. Open the Package Manage Console: Tools->Nuget Package Manager->Package Manager Console
  2. Type cd {path where your csproj file resides} (this is important)
  3. Now type dotnet ef migrations add InitialMigration

Upvotes: 12

Akshay Mishra
Akshay Mishra

Reputation: 1713

sometimes you need to change the current directory in console/terminal eg:

PM> cd E:\Projects\CrossTest\
PM> dotnet ef migrations add InitialMigration

and Align your package versions. Either use preview1 packages or preview2. Mix of those are not supported.

Upvotes: 123

susieloo_
susieloo_

Reputation: 1519

The dotnet-ef command has moved.

You will need to add a reference to Microsoft.EntityFrameworkCore.Tools.DotNet AND Microsoft.EntityFrameworkCore.Design to your dependencies in project.json, then add Microsoft.EntityFrameworkCore.Tools.DotNet to the tools section and you should be good to go.

Cited from: http://errummwelluhh.blogspot.com

Upvotes: 0

Artur Karbone
Artur Karbone

Reputation: 1658

Just faced similar issue. Fixed by downgrading to 1.0.0-preview3-final

"tools": {
     "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.0.0-preview3-final",    
}

and changing --project param to --startup-project

dotnet ef --startup-project <PATH_TO_PROJECT_DIRECTORY> migrations add <MIGRATION_NAME>

In global.json I also downgraded version to

 "sdk": {
     "version": "1.0.0-preview2-003131"
 }

This might be a temp workaround before migrating to csproj.

Upvotes: 2

Gys Rademeyer
Gys Rademeyer

Reputation: 360

Instead of:

"tools": {
    "Microsoft.EntityFrameworkCore.Tools.DotNet":"1.0.0"
  },

try:

"tools": {
      "Microsoft.EntityFrameworkCore.Tools.DotNet": {
      "version": "1.0.0-preview3-final"
  }},

Upvotes: 15

Related Questions