Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cache mismatching in NET Core project due to framework packages can be in the SDK or NuGet folder

Open
#128 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
build-system

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.

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.

Dominant language
C#
Stars
64
Forks
24
Avg merge
1d 14h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/MSBuildCache

All issues in microsoft/MSBuildCache

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.