Consider onboarding NuGet.Client onto the .NET Arcade build infrastructure to better support the .NET source-build project. Currently because NuGet.Client is not on arcade, an Arcade shim is utilized. The shim is missing functionality such a prebuilt detection.
Aside from making source-build easier, there are a couple other speculative benefits:
It may be easier to deal with MSRCs
Nuget would get all the compliance scanning arcade provides with minimal setup
This is not a trivial amount of work but I wanted to start a conversation about the feasibility and cost/benefits of this work. Additionally having an issue will allow us to link issues that would benefit from this work.
Consider onboarding NuGet.Client onto the .NET Arcade build infrastructure to better support the .NET source-build project. Currently because NuGet.Client is not on arcade, an Arcade shim is utilized. The shim is missing functionality such a prebuilt detection.
Aside from making source-build easier, there are a couple other speculative benefits:
This is not a trivial amount of work but I wanted to start a conversation about the feasibility and cost/benefits of this work. Additionally having an issue will allow us to link issues that would benefit from this work.