microsoft / microsoft/MSBuildSdks
Notargets overriding GetFrameworkPaths causes warnings
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 508
- Forks
- 94
- Avg merge
- 6h 40m
- Merged PRs (30d)
- 2
Description
After a recent change in NoTarget SDK, GetFrameworkPaths has become stubbed.
This causes warnings to appear if any .NET PackageReference is used, because ResolvePackageAssets will pick up and emit standard Framework dependencies as FrameworkAssemblies and feed them into ResolveAssemblyReference, which will be unable to resolve those standard references, because .NET framework SDK path is no longer set
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
No files or tests are identified. Start by tracing the NoTarget SDK's GetFrameworkPaths behavior and how ResolvePackageAssets feeds framework dependencies into ResolveAssemblyReference. Done means projects using .NET PackageReference no longer emit warnings and standard framework references resolve correctly.
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