Installing Visual Studio Build Tools in a container is one of the worst experiences for a real value prop to containerization

Describe the bug
There are no pre-built WCOW images with Visual Studio build tooling from Microsoft.

To Reproduce
Trying to author your own... I am constantly battling issues with how slow and buggy installing and using Visual Studio inside a container is.

Expected behavior
Just give me a WCOW image that I can do

COPY --from=mcr.microsoft.com/visualstudio:17 "C:/Program Files/Visual Studio/" "C:/Program Files/Visual Studio/"

as my installation step. It's 2025, it should be possible to put a bunch of files on a disk in the right places from archives when interacting with the Microsoft ecosystem. Or make winget work. Or anything really. Somehow, the product experience on Linux, which doesn't have product designers, is better!

Configuration:

• Edition: Server 2022

Additional context
It would be nice if you guys contributed to buildkit because the reliance on whatever the classic Docker builder is doing is crazy. Surely you must be using something else to build container images.

Reproduce the Server 2022 workflow for installing Visual Studio Build Tools in a WCOW container, then review the proposed mcr.microsoft.com/visualstudio:17 image and the mentioned winget and buildkit paths. Done means a supported path that avoids the reported slow, buggy installation and enables the requested COPY-style use.