VS 2017 RC error: Cannot find project info for... This can indicate a missing project reference
See original GitHub issueSteps to reproduce
- Create ASP.Core project (.NET Framework), then update to latest Nuget packages;
- Create Class Library 1 (.NET Framework), add Microsoft.EntityFrameworkCore.SqlServer nuget package
- Create Class Library 2 (.NET Framework), add Microsoft.EntityFrameworkCore.Relational nuget package
- Compile to test: solution should be possible to compile
- Create References: add project reference “Library 1” to “Library 2” add project reference “Library 2” to ASP.Core
- Compile
Expected behavior
Compiled solution. Or compilation error message that contains useful information.
Actual behavior
Compilation error
Environment data
dotnet --info
output:
.NET Command Line Tools (1.0.0-preview4-004233)
Product Information: Version: 1.0.0-preview4-004233 Commit SHA-1 hash: 8cec61c6f7
Runtime Environment: OS Name: Windows OS Version: 10.0.14393 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\1.0.0-preview4-004233
Solution:
Issue Analytics
- State:
- Created 7 years ago
- Reactions:11
- Comments:54 (9 by maintainers)
Top Results From Across the Web
VS 2017 RC error: Cannot find project info for... This ...
This can indicate a missing project reference... My problem was that I was targeting net452 in the class library I was referencing in...
Read more >Visual Studio 2017 error: Cannot find project info for "" This ...
Referenced project's path stored in .csproj is case sensitive! So, be aware, and check if you have the correct path in correct case!...
Read more >VS 2017 RC error: Cannot find project info for... This can ...
VS 2017 RC error: Cannot find project info for... This can indicate a missing project referenceClosed - Lower Priority0 2.
Read more >Troubleshoot broken references - Visual Studio
Fix a broken project reference · In Solution Explorer, right-click your project node, and then select Properties. The Project Designer appears.
Read more >Cannot find project info for 'project'. This can indicate a ...
While trying out migrating a few old projects to ASP.NET Core 1.1, I stumbled upon this error when trying to the build the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Okay so the issue is that transitive dependencies do not work. If Project A references Project B, then Project A must (at the moment) directly reference the projects referenced in Project B.
For example: if
A
referencesB
andB
referencesC
, to get rid of this errorA
must referenceB
andC
directly.This issue is marked closed but I’m seeing it with the released VS 2017, how do I fix it? I tried adding all the references to my .NET Core project still no luck