microsoft / microsoft/PowerToys
Add automatic check of .vsconfig file entries
- Dominant language
- C
- Stars
- 139k
- Forks
- 8.6k
- PR merge metrics
- PR metrics pending
Description
### Microsoft PowerToys version
0.00.0
### Installation method
Other (please specify in "Steps to Reproduce")
### Area(s) with issue?
General
### Steps to reproduce
When running `setup-dev-environment.ps1`, the following .vsconfig entries are currently unavailable.
```
"Microsoft.VisualStudio.Component.Windows10SDK.19041",
"Microsoft.VisualStudio.Component.Windows10SDK.20348",
"Microsoft.VisualStudio.Component.Windows10SDK.22621",
"Microsoft.VisualStudio.Component.Windows10SDK.26100",
"Microsoft.VisualStudio.ComponentGroup.WindowsAppSDK.Cs"
```
### ✔️ Expected Behavior
All entries in .vsconfig file are available.
### ❌ Actual Behavior
VS installer indicates that the specified files are unavailable.
### Upload Bug Report ZIP-file
_No response_
### Additional Information
Entries in .vsconfig will regularly come and go, so it seems natural to have automatic checks and remediation to avoid periodic issues.
### Other Software
_No response_
Contributor guide
Research direction
Start by reading and running setup-dev-environment.ps1 alongside the repository’s .vsconfig entries. Determine how unavailable entries should be detected and remediated as Visual Studio components change. Done means the setup process checks the listed entries and handles unavailable components without leaving the configuration unusable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100