-
Notifications
You must be signed in to change notification settings - Fork 815
Use .NET10p3 SDK #18471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Use .NET10p3 SDK #18471
Conversation
|
Hm, some source build (presumably) issues, I can fix them, please ping me next week. |
@vzarytovskii : Ping, do you have an ideas what caused it? |
Judging by the plain builds working fine, some arcade shenanigans. I've updated on top of main, let me see what fails and how can I fix it. |
@ViktorHofer @baronfel getting a bunch of following by just upgrading SDK to 10p3:
I haven't seen it before, does this ring a bell by any chance? |
Heyho. This is a new NuGet feature in the .NET 10 SDK. See https://learn.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files#how-prunepackagereference-works for more details. The gist is that the package references that are already provided by the shared frameworks used (usually Microsoft.NETCore.App) are unnecessary and should be removed. I.e. System.Text.Json is already provided inbox on .NETCoreApp TFMs. |
Thanks! Huh, good to know. How does it play together with netfx? If we build both core and desktop compilers? Or is it purely build-time feature (where to copy assemblies from?)? |
For multi-targeting projects you want to condition PackageReference items on the TFMs that need them. |
Thanks. Btw, when conditionally aded the
Had to ignore the warning. |
It's roughly this time of the year, when F# is switching to the new preview SDKs, to start testing BCL and CLR changes. Switching of the TFM usually happens around summer.