microsoft / microsoft/winget-pkgs
[Package Issue]: Microsoft.VisualStudio.2022.BuildTools only installs C# build tools
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Please confirm these before moving forward
- I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue
Other
Brief description of your issue
I did winget install 'Microsoft.VisualStudio.2022.BuildTools' and got no errors or anything, but only the C# build tools got installed. Maybe this is by design, but I'm looking for a way for WinGet to install C++ build tools.
If this is by design, then this package should be renamed to Microsoft.VisualStudio.2022.BuildTools.C# and another package should be created named Microsoft.VisualStudio.2022.BuildTools.C++
I was able to do what I was looking for by not using winget and running the installer with:
.\vs_BuildTools.exe --passive --wait --add Microsoft.VisualStudio.Workload.VCTools --includeRecommended
Steps to reproduce
winget install 'Microsoft.VisualStudio.2022.BuildTools'
Actual behavior
only C# tools are installed
Expected behavior
c++ tools installed.
Environment
Windows Package Manager v1.3.2691
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.22623.885
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0
Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
Links
---------------------------------------------------------------------------
Privacy Statement https://aka.ms/winget-privacy
License Agreement https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
Screenshots and Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Microsoft.VisualStudio.2022.BuildTools package manifest in the winget-pkgs repository and compare its installer configuration with the reported command. Check how Visual Studio workloads are represented in the manifest and whether the requested VCTools workload can be selected. Done means the package behavior or naming clearly provides a reproducible way to install the C++ build tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, csharp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100