Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
If your solution has projectreferences that refer to the same project, with different casing, restore may not work. This also affects different relative paths, without a difference in casing #4574
Details about Problem
NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe): nuget.exe, msbuild /t:Restore
Detailed repro steps so we can see the same problem
Several errors will be reported. Root cause of problem is using path "....\services\Proj1\Proj1.csproj" instead of "....\Services\Proj1\Proj1.csproj" in file "BusinessLogic\Proj3\Proj3.csproj".
Solution could be built inside VS 2017 without problems.
Let's dig into this one and understand the problem. Do nuget.exe and msbuild /t:restore have a problem that VS and dotnet.exe don't?
@rrelyea so i have confirmed that you can never get to this inconsistent casing using a tool like VS, or the
However, the issue is not as simple as i thought, this only repro's when more than one project( say ProjB and ProjC) reference a project (say ProjA) such that the casing of their reference is inconsistent. Something like this:
The incosistency of casing in f in FolderA is what causes this issue.
In this case the relative path string are different.