dotnet / dotnet/project-system

No ActiveConfiguration on new project causes EFCore migration .deps.json does not exist error

Open
#6,785 4 comments 0 reactions 0 assignees View on GitHub
Triage-Investigate
Dominant language
C#
Stars
1k
Forks
415
PR merge metrics
No merged PRs in 30d

Description

**Visual Studio Version**: VS2019 16.8.3

**Summary**: I was asked by the EFCore team to post here since it seems it's related to the project-system. I created a brand new project, added EFCore to it with a simple blog.cs class, then tried to add migration and received the dllname.deps.json file not found:

![image](https://user-images.githubusercontent.com/4919080/101673799-a0265600-3a25-11eb-82da-3679602d4e40.png)

@bricelam asked me to run some commands to get more details on the problem:

![image](https://user-images.githubusercontent.com/4919080/101673899-c5b35f80-3a25-11eb-9170-aee2ca1c5a2a.png)

The only thing I did is create a new .Net 5 project, nothing else.

My project conf with my configuration manager details:

![image](https://user-images.githubusercontent.com/4919080/101674071-057a4700-3a26-11eb-903e-a106f0b47bee.png)

Reference to this case: https://github.com/dotnet/efcore/issues/23607

I also joined the .zip of the project. Please help, I haven't been able to run ef core commands from package manager console for like almost a year now.
[TestEFMigration.zip](https://github.com/dotnet/project-system/files/5668056/TestEFMigration.zip)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.