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

Question

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.

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 :(

I don't know your issue but I'll point out the --project is in the wrong spot. `dotnet ef` is different than `dotnet` and that's the command that needs the --proj. Also if you're using the latest tooling, you will need to migrate from project.json to the .csproj format. If you install Visual Studio 2017 this WILL break the preview tooling that was available with VS 2015 so only install it if everyone working on the project is ready to switch. — Erik Noren, Mar 24 '17 at 06:47
Thanks Erik. Is it possible to migrate from `project.json` to `.csproj` without needing to upgrade to Visual Studio 2017? Or do I have to absolutely do both the project upgrade and VS upgrade for this to work? — Shiva, Mar 24 '17 at 19:34
I wouldn't move to .csproj unless you were going to use an IDE that supported it. Check out Gys' answer below. The preview tooling should still be set up for project.json configuration. In general, the tooling you'll want to keep at preview for project.json support but the other libraries you should be able to use latest versions. — Erik Noren, Mar 24 '17 at 20:38
"Do we have no choice but to Install Visual Studio 2017 and start from scratch??" Sadly and eventually, [yes](http://stackoverflow.com/questions/38536978/is-project-json-deprecated#38537047). — trevorc, Mar 24 '17 at 22:33

score 108 · Answer 1 · answered Jun 10 '18 at 03:53

108

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.

answered Jun 10 '18 at 03:53

Akshay Mishra

1,535
2
15
14

5

This was the case for me. I had to encase the entire path within the double quotes. `PM> cd "E:\Projects\CrossTest\"` and it worked like charm for me. – Virag Dilip Desai Aug 02 '18 at 12:55
8

This reply, `cd MyProjectSubfolder` is probably the "correct" answer for most of the people who hit this page. It worked for me :) – paulsm4 Nov 24 '18 at 23:41
1

tried defferent way, but no working, cd "C:\pp\EmployeeApp" and cd C:\pp\EmployeeApp then execute command - dotnet ef migrations add InitialCreate. same issue came – Sajith Jul 10 '19 at 13:06
Please make sure you added nuget Microsoft.EntityFrameworkCore.tools and Design packages. – Akshay Mishra Jul 10 '19 at 14:43
2

@AkshayMishra Thanks a lot, this was my problem and I had to use cd to point to the right project directory. day savior! – PatsonLeaner Mar 18 '20 at 08:40
3

This is the least intrusive answer, and worked for me as well using .Net Core 5.0. I just had to point to correct directory without changing any config. – stack underflow Dec 08 '20 at 05:23

TAHA SULTAN TEMURI · Answer 2 · 2019-11-15T09:06:17.407

50

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

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.

edited Nov 15 '19 at 09:06

answered Sep 25 '19 at 10:18

TAHA SULTAN TEMURI

4,031
2
40
66

6

Thanks. That was my issue. After running the "dir" command it initially looked like the correct folder but then when I looked through Windows Explorer I saw that I needed to go one more folder deeper to get to the location of the .csproj file. Went to that directory and then ef migrations add command ran. – Caverman Jun 12 '20 at 03:33
Glad to help you – TAHA SULTAN TEMURI Jul 04 '20 at 05:12
Had the same issue! Thanks mate. Is there any way to see the current dir instead of the nonsense "PM>"? – Florent Aug 22 '20 at 15:37
@Florent glad to help you , did you check this https://stackoverflow.com/questions/607670/windows-shell-command-to-get-the-full-path-to-the-current-directory? – TAHA SULTAN TEMURI Aug 22 '20 at 15:45
1

As simply as that :). Thank you – Lug May 19 '21 at 15:20
So nice to help you @Lug – TAHA SULTAN TEMURI May 19 '21 at 16:15
If it helped , please dont forget to buymeacoffee https://www.buymeacoffee.com/tahatemuri thanks – TAHA SULTAN TEMURI Jul 03 '22 at 13:21

score 15 · Accepted Answer · edited Mar 24 '17 at 18:41

15

Instead of:

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

try:

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

edited Mar 24 '17 at 18:41

svick

236,525
50
385
514

answered Mar 24 '17 at 07:35

Gys Rademeyer

360
2
8

10

thanks, that why I highly not recommend anyone doesn't use ASP.NET Core until v3.x.x, it is dependency hell and version hell. – Cheung Jul 24 '17 at 04:03

score 12 · Answer 4 · answered Aug 26 '18 at 17:17

12

Add the nuget package Microsoft.EntityFrameworkCore.Tools
Add the nuget package Microsoft.EntityFrameworkCore.Design
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)

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

answered Aug 26 '18 at 17:17

QuranX Administrator

395
1
3
10

This helped me get a bit further. I get this now: Unable to create an object of type '***Context'. Add an implementation of 'IDesignTimeDbContextFactory<***Context>' to the project, or see https://go.microsoft.com/fwlink/?linkid=85172 8 for additional patterns supported at design time. I'll have a look at that link – willDaBeast Nov 27 '18 at 15:25
The fifth step is the most important.I did it – Farb Dec 24 '19 at 06:55

score 2 · Answer 5 · answered Mar 28 '17 at 09:32

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.

where to find this tools in visual studio ?? – SULPHURIC ACID Jan 04 '23 at 07:04 — SULPHURIC ACID, Jan 04 '23 at 07:04

score 2 · Answer 6 · answered Oct 14 '21 at 05:14

2

Just simply use this command.

Add-Migration InitialCreated -c bodoContext

No need to worry.

answered Oct 14 '21 at 05:14

Shakir Ahmed

559
4
13

score 1 · Answer 7 · answered Jan 18 '21 at 17:56

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.

score 0 · Answer 8 · edited Jun 20 '20 at 09:12

0

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

edited Jun 20 '20 at 09:12

Community

1
1

answered May 09 '17 at 20:10

susieloo_

1,391
1
16
22

score 0 · Answer 9 · answered Mar 17 '23 at 14:34

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

score 0 · Answer 10 · answered Apr 10 '23 at 08:34

0

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

answered Apr 10 '23 at 08:34

thp3loN2

27
2

score 0 · Answer 11 · answered Jun 23 '23 at 13:03

0

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".

answered Jun 23 '23 at 13:03

Enes Şağban

1

score -1 · Answer 12 · answered Aug 14 '21 at 13:35

-1

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

answered Aug 14 '21 at 13:35

devknight

47
3

2

Please don't [repeat answers](https://stackoverflow.com/a/52028573/861716). It only adds noise. – Gert Arnold Aug 15 '21 at 15:28

score -1 · Answer 13 · answered Apr 07 '23 at 13:57

-1

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

dotnet ef database update -c ApplicationDbContext

answered Apr 07 '23 at 13:57

sweetnandha cse

705
7
16

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

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

13 Answers13

Linked