Jacques Eloff

@NikolaMilosavljevic I'll probably push to the internal branch to test the signing/publishing steps for Visual Studio. @MichaelSimons Do we need to exclude anything here for source build? This is Windows+VS...

@marcpopMSFT since we plan on removing this from VS, you still want me to merge this so we have a copy?

The path for one of the log files is too long: 262 (max path is 260). Can you redirect WinGet to generate the log in different folder? The problem is...

cc @mthalman

The standard log file format for the SDK would be something like `Microsoft_.NET_SDK_6.0.202_(x64)_20230627230259` so something on the WinGet size is modifying it to a longer name. The problem becomes worse...

I'd suggest jumping to 3.11.2 - it has the latest security fixes

You can also override the displayed language by launching the bundle and passing "/lang 1033" or one of the other supported LCIDs.

With regards to the namespace question...I see this as something that the SDK might use, but most applications would be outside the SDK space, e.g. a global tool to query...

Fixing up the workload automation is next on my list :)

I'm looking a number of issues. - For .NET 8, the drop.exe tool failed with multiple issues - I'm following up with the owners on that. - The generated XML...