Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SDK doesn't honor TargetingPackVersion on FrameworkReference
See original GitHub issueSDK permits specifying TargetingPackVersion metdata on FrameworkReference: https://github.com/dotnet/sdk/blob/7d6b26df6cc873e07816a098bb66a6bde2640b06/src/Tasks/Microsoft.NET.Build.Tasks/ResolveFrameworkReferences.cs#L99-L103
But then it constructs the path to the targeting pack based on KnownFrameworkReference: https://github.com/dotnet/sdk/blob/7d6b26df6cc873e07816a098bb66a6bde2640b06/src/Tasks/Microsoft.NET.Build.Tasks/ResolveFrameworkReferences.cs#L112-L122
Also, is this really the way we should be specifying which framework to build against? I had expected RuntimeFrameworkVersion to work, but it looks like that only controls the runtime and not ref-pack.
/cc @dsplaisted
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I see. Did you consider a property for this, or is that not so interesting in light of multiple frameworks? /cc @natemcmaster @zsd4yr @vatsan-madhavan
This should be fixed. RuntimeFrameworkVersion doesn’t affect the targeting pack version, as once we release the runtime and the targeting packs will be patched independently.