-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"error NETSDK1007: Cannot find project info" when a csproj with a certain name depends on another in the same directory. #2779
Comments
Reproduced this same issue while trying to generate csprojs all in the same directory. |
Everything was working fine in the same situation with 2 F# projects in the same directory, but after I added nuget package today I have received the same error. dotnet --version /usr/share/dotnet/sdk/2.2.104/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.targets(129,5): error NETSDK1007: Cannot find project info for '/home/.../aproject.fsproj'. This can indicate a missing project reference. [/home/.../aproject.fsproj] If I do Reverted changes, deleted The started Eventually moved one of the projects into a separate folder |
…0190906.2 (#2779) - Microsoft.Build - 16.3.0-preview-19456-02
… merges/release/3.0.100-preview9-to-release/3.0.1xx * upstream/release/3.0.100-preview9: (21 commits) Update dependencies from https://github.com/Microsoft/msbuild build 20190906.2 (#2779) Update dependencies from https://github.com/dotnet/cli build 20190908.6 (#2728) Update dependencies from https://github.com/dotnet/sdk build 20190908.1 (#2726) Update dependencies from https://github.com/dotnet/cli build 20190908.2 (#2715) Update dependencies from https://github.com/aspnet/websdk build 20190908.1 (#2713) Update dependencies from https://github.com/dotnet/cli build 20190907.12 (#2710) Update dependencies from https://github.com/dotnet/cli build 20190907.11 (#2707) Update dependencies from https://github.com/aspnet/websdk build 20190907.5 (#2706) Update dependencies from https://github.com/dotnet/cli build 20190907.9 (#2705) Update dependencies from https://github.com/aspnet/websdk build 20190907.4 (#2704) Update dependencies from https://github.com/aspnet/AspNetCore-Tooling build 20190907.3 (#2702) Update dependencies from https://github.com/aspnet/AspNetCore-Tooling build 20190906.6 (#2675) Update dependencies from https://github.com/dotnet/cli build 20190906.12 (#2670) Update dependencies from https://github.com/dotnet/sdk build 20190906.2 (#2669) Update dependencies from https://github.com/Microsoft/msbuild build 20190905.2 (#2666) Update dependencies from https://github.com/dotnet/core-setup build 20190906.20 (#2668) Update dependencies from https://github.com/dotnet/cli build 20190906.11 (#2667) Update dependencies from https://github.com/dotnet/core-setup build 20190906.12 (#2659) Update dependencies from https://github.com/aspnet/AspNetCore-Tooling build 20190905.12 (#2633) Update dependencies from https://github.com/Microsoft/msbuild build 20190830.3 (#2618) ... Conflicts: eng/Version.Details.xml eng/Versions.props
…elease/3.0.1xx-to-release/3.1.1xx * upstream/release/3.0.1xx: (231 commits) [release/3.0.1xx] Update dependencies from microsoft/vstest (#2809) Update dependencies from https://github.com/dotnet/cli build 20190911.11 (#2823) Update dependencies from https://github.com/aspnet/websdk build 20190911.2 (#2816) Update dependencies from https://github.com/dotnet/cli build 20190911.1 (#2807) Update dependencies from https://github.com/dotnet/cli build 20190910.6 (#2803) Update dependencies from https://github.com/aspnet/AspNetCore-Tooling build 20190910.12 (#2801) Update dependencies from https://github.com/dotnet/cli build 20190910.5 (#2799) Update dependencies from https://github.com/aspnet/websdk build 20190910.5 (#2798) Update dependencies from https://github.com/aspnet/AspNetCore-Tooling build 20190910.5 (#2797) Update dependencies from https://github.com/dotnet/arcade build 20190910.3 (#2796) Update dependencies from https://github.com/dotnet/cli build 20190910.4 (#2794) Update dependencies from https://github.com/aspnet/websdk build 20190910.4 (#2795) [release/3.0.1xx] Update dependencies from aspnet/AspNetCore-Tooling (#2759) Update dependencies from https://github.com/aspnet/websdk build 20190910.2 (#2792) Update dependencies from https://github.com/dotnet/core-setup build 20190910.02 Update dependencies from https://github.com/dotnet/arcade build 20190909.10 (#2788) Update dependencies from https://github.com/dotnet/core-setup build 20190909.40 (#2781) Update dependencies from https://github.com/Microsoft/msbuild build 20190906.2 (#2779) Update dependencies from https://github.com/dotnet/core-setup build 20190909.33 (#2775) Update dependencies from https://github.com/dotnet/cli build 20190909.10 (#2771) ... Conflicts: eng/Version.Details.xml eng/Versions.props
From @davedissian on December 29, 2018 14:42
If I have two csproj's within the same directory, where csproj (1) depends on csproj (2), I get a NETSDK1007 error if the dependency (2) has a name which is lexicographically greater than the root project (1). For example, if I have
Worker.csproj
which depends onLibrary.csproj
, it compiles fine. However, If I haveAWorker.csproj
which depends onLibrary.csproj
, I get anNETSDK1007
error.I guess the cause might have something to do with dependency resolution only being a single pass process (rather than being a two pass process that stores projects in a lookup table before resolving them).
Steps to reproduce
I have attached a zip file with 3 solutions: NETSDK1007-issue.zip
AWorker.csproj
andLibrary.csproj
Worker.csproj
andLibrary.csproj
AWorker.csproj
andLibrary\Library.csproj
If I try and run
dotnet build Worker.sln
insideBroken
, I get the following output:The project files look like this:
AWorker.csproj
:Library.csproj
:Expected behavior
It compiles successfully.
Environment data
OS info:
macOS Mojave 10.14.2
If applicable, version of the tool that invokes MSBuild (Visual Studio, dotnet CLI, etc):
Copied from original issue: dotnet/msbuild#4035
The text was updated successfully, but these errors were encountered: