Open Alovchin91 opened 3 years ago
I've sent feedback to the VS team to combine all the Windows related workloads in a single workload: https://developercommunity.visualstudio.com/t/Combine-C-desktop-NET-Desktop-and-UW/1454966?entry=suggestion. While it won't be lightweight, it requires less clicks to install.
I think it's better to keep separate workload for C++ and C# if it's possible because somme devs works only with one language (C++ or C#) these devs need language specific workload (like the WinAppSDK VSIX). Concerning desktop and UWP yes I think it's good to merge it. So two workloads
It's should be good if the associated WinAppSDK VSIX will be included to the new workloads.
Today the UWP development workload only installs .NET by default and for C++ you need to select from the sidebar. C++ developers might not need .NET tools but currently it must be installed as well.
We are working on adding the Windows App SDK as part of .NET and C++ VS2022 workloads. We are currently targeting VS2022 17.1 Preview 1, We removed several dependencies from the UWP workload and split the WinAppSDK vsix into these two components: .NET and C++, making them lighter and saving several gigabytes.
So that, in VS 2022 17.1, .NET developers who want to use the WindowsAppSDK, will only need to install the .NET workload and select the Windows App SDK component. C++ developers will have a similar experience.
Proposal: A lightweight Visual Studio workload
Summary
Provide a lightweight Visual Studio workload for building Windows App SDK / WinUI 3 apps. "Lightweight" meaning not much more on top of existing C++ and C# workloads.
Rationale
Currently, using Windows App SDK / WinUI 3 requires installing Universal Windows Development workload for Visual Studio. Its size differs depending on components already installed. For example, for my setup with C# and C++ workloads and Windows SDK 19041 already installed it still adds ~9 GB.
I don't know what exactly is needed there on top of existing workloads, but it feels like a huge overkill, especially if I only plan to develop non-packaged desktop apps.
Please consider providing more granular control over Visual Studio components when installing Windows App SDK / WinUI 3 workload.