microsoft / microsoft/MSBuildCache
Cache mismatching in NET Core project due to framework packages can be in the SDK or NuGet folder
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 64
- Forks
- 24
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
Description
When projects are using NET 9 SDK to build NET 8 binaries, the framework target package can be in the NuGet folder or SDK folder (if they installed NET 8 SDKs)
it leads different fingerprints on different machine configurations, and cause cache miss on Dev environment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the cache behavior with a .NET 9 SDK building .NET 8 binaries on machines where the framework target package is resolved from either the NuGet or SDK folder. Trace how those package locations contribute to cache fingerprints. Done means equivalent builds produce consistent fingerprints and avoid environment-dependent cache misses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100