microsoft / microsoft/WindowsDeveloperConfig
Should not default to Visual Studio Community 2026? why it still default to Visual Studio Community 2022?
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 2.2k
- Forks
- 168
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 5
Description
Should not default to Visual Studio Community 2026? why it still default to Visual Studio Community 2022?
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 where the repository defines or selects the default Visual Studio version, then compare that configuration with the versions supported by the setup workflow. Confirm the intended default with the issue context or project guidance; done means the setup selects the agreed version consistently and the relevant behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100