Enable-Migrations - Cannot bind argument to parameter 'Path'

Question

I'm new to ASP.NET and am trying to set up a webAPI c# application with entity framework. But when I try to run the Enable-Migrations command on nuget-package-manager console, I'm getting the following error:

"Cannot bind argument to parameter 'Path' because it is null"

    enable-migrations : Cannot bind argument to parameter 'Path' because it is 
    null.
    At line:1 char:1
    + enable-migrations -ContextTypeName SchoolDBContext
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Enable-Migrations], 
    ParameterBindingValidationException
    + FullyQualifiedErrorId : 
    ParameterArgumentValidationErrorNullNotAllowed,Enable-Migrations

I've tried uninstalling and re-installing entity framework but it still gives the same error.

How can I fix this?

github.com/aspnet/EntityFramework6/issues/1290

madreflection
– madreflection

2019-09-27 17:25:59 +00:00
Commented Sep 27, 2019 at 17:25 — madreflection
– madreflection, Commented Sep 27, 2019 at 17:25

rjs123431 · Accepted Answer · 2019-09-27 16:10:15Z

12

I had this error when using EntityFramework 6.3.0, downgrading it to 6.2.0 fix my issue.

answered Sep 27, 2019 at 16:10

rjs123431

6884 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Piumi Perera Over a year ago

wow thanks a lot. Downgrading to 6.2 fixed it for me as well!

T M Over a year ago

in my case vs needed a restart also ;)

Kinexus Over a year ago

I would add that 6.4.0 is available and the downgrade should not be required as the upgrade (from 6.3.0) fixed my issue.

Bob Koury Over a year ago

Holy cats! I've been messing around with this so long it's embarrassing. It was broken for me in EF 6.4, broken in EF 6.3, works in EF 6.2. Thanks!

Bob Koury Over a year ago

It seems like Microsoft EntityFramework Core is now the focus, not EntityFramework. Does it make sense to hope a problem to get EntityFramework 6.4 fixed? I'm not sure how to do it.

poul_ko · Accepted Answer · 2019-11-08 08:49:52Z

4

There is a workaround for this bug. Just edit a file and restart Visual Studio. It works!

answered Nov 8, 2019 at 8:49

poul_ko

3472 silver badges6 bronze badges

Comments

Shadman · Accepted Answer · 2019-12-14 09:57:42Z

4

I had same error and just update EF to latest version (Here to 6.4.0) Now migrations works well.

update-package entityframework
enable-migrations
Add-Migration InitialCreate

answered Dec 14, 2019 at 9:57

Shadman

1513 silver badges11 bronze badges

Comments

Mahmud · Accepted Answer · 2019-11-06 10:09:40Z

2

Just use any of the versions of EntityFramework except 6.3.0. In my case using EntityFramework 6.0.0 solved the problem.

answered Nov 6, 2019 at 10:09

Mahmud

4015 silver badges13 bronze badges

Comments

DLeh · Accepted Answer · 2021-09-28 13:55:26Z

1

Updating EntityFramework packages in my solution from 6.3.0 to 6.4.4 resolved the issue for me.

answered Sep 28, 2021 at 13:55

DLeh

24.6k17 gold badges95 silver badges141 bronze badges

Comments

Shewan · Accepted Answer · 2019-09-25 14:16:35Z

0

Have you tried manually adding a database with the appropriate name to match the connection string in your config file?

I had an identical error this afternoon. Adding the database manually fixed the issue and I have subsequently managed to add a migration which added a table.

Following this I removed the Configuration file and the migrations (from the project's 'Migrations' folder), and deleted the database. When I subsequently ran update-database I got the more conventional responses:

Checking if the context targets an existing database...

Code First Migrations enabled for project MyProject.Domain

I then ran 'add-migration Initial' and 'update-database'. This seeded me a new database. All good. Any updates from others about underlying story gratefully appreciated.

edited Sep 25, 2019 at 14:16

answered Sep 25, 2019 at 13:49

Shewan

811 silver badge11 bronze badges

2 Comments

Piumi Perera Over a year ago

I tried manually adding the database but for me it's still producing the same error. But thank you for your input.

Shewan Over a year ago

Perhaps you could add a little more detail. For example, you say that you have installed Entity Framework to your project, I assume you have added an appropriate connection string to your web.config or app.config file, you have added a context that inherits System.Data.Entity.DbContext and has the appropriate constructors.

Stephen Barriball · Accepted Answer · 2019-10-17 10:30:01Z

0

I get this if I have my database code in a separate class library. To get the commands to work I had to select the class library as the start up project.

So I did the following...

Select the project where the database context exists and right click, select "Set as StartUp Project".

Select the default project as the correct project.

Ensure that you are in the project directory on the filesystem.

Run the commands.

answered Oct 17, 2019 at 10:30

Stephen Barriball

1

Comments

prinujith kj · Accepted Answer · 2019-11-17 05:57:46Z

0

Issue is due to not having sufficient privileges to run the command. Open Visual studio in administrator mode (Run as Administrator) and execute the command.

answered Nov 17, 2019 at 5:57

prinujith kj

791 silver badge2 bronze badges

Comments

ti55 · Accepted Answer · 2021-01-08 19:45:03Z

0

re-installing EF 6.4.4 after uninstalling 6.1.3 resolved this for me.

answered Jan 8, 2021 at 19:45

ti55

12 bronze badges

Collectives™ on Stack Overflow

Enable-Migrations - Cannot bind argument to parameter 'Path'

9 Answers 9

5 Comments

Comments

Comments

Comments

Comments

2 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

9 Answers 9

5 Comments

Comments

Comments

Comments

Comments

2 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related