Nuget package file path casing incorrect on Linux

bagoette commented 1 year ago

Describe the bug

My project is using private NuGet feeds, and after a successful dotnet restore, build and test both fail due to not being able to find our private packages in the ~/.nuget/packages/ folder.
It appears to be a case sensitivity issue
The restore command is storing the packages with lower case names, and for some reason build and test are looking for the actual capitalized name.

bagoette@DevBox:~/code/webapi$ dotnet build --interactive

MSBuild version 17.4.3+7e646be43 for .NET

  Determining projects to restore...

  All projects are up-to-date for restore.

/usr/lib/dotnet/sdk/7.0.105/Microsoft.CSharp.CurrentVersion.targets(129,9): warning MSB3884: Could not find rule set file "/home/bagoette/.nuget/packages/Lrm.StyleCop/1.0.4/Lrm.ruleset". [/home/bagoette/code/webapi/WebApi.Generators/WebApi.Generators.csproj]

To Reproduce

I don't know how to direct you to a reproducible repo since it requires private nuget feeds.
Our project is normally developed on Windows, and cloning the repo onto a Linux machine, dotnet build fails instantly

Further technical details

Include the output of dotnet --info

.NET SDK: Version: 7.0.105 Commit: e1bc5e001c

Runtime Environment: OS Name: ubuntu OS Version: 22.04 OS Platform: Linux RID: ubuntu.22.04-x64 Base Path: /usr/lib/dotnet/sdk/7.0.105/

Host: Version: 7.0.5 Architecture: x64 Commit: 8042d61b17

.NET SDKs installed: 7.0.105 [/usr/lib/dotnet/sdk]

.NET runtimes installed: Microsoft.AspNetCore.App 7.0.5 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 7.0.5 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]

Other architectures found: None

Environment variables: Not set

global.json file: Not found

ghost commented 1 year ago

Thanks for creating this issue! We believe this issue is related to NuGet tooling, which is maintained by the NuGet team. Thus, we closed this one and encourage you to raise this issue in the NuGet repository instead. Don’t forget to check out NuGet’s contributing guide before submitting an issue!

If you believe this issue was closed out of error, please comment to let us know.

Happy Coding!

bagoette commented 10 months ago

I think this was closed out of error. I don't think this is a NuGet issue because the restore command works correctly. But build/test both fail.

dotnet / sdk