Skip to content

feat(CmdPal): add .vsconfig to extension template#47000

Open
SAY-5 wants to merge 1 commit intomicrosoft:mainfrom
SAY-5:feat/cmdpal-template-vsconfig
Open

feat(CmdPal): add .vsconfig to extension template#47000
SAY-5 wants to merge 1 commit intomicrosoft:mainfrom
SAY-5:feat/cmdpal-template-vsconfig

Conversation

@SAY-5
Copy link
Copy Markdown

@SAY-5 SAY-5 commented Apr 13, 2026

Summary of the Pull Request

When opening the CmdPal extension template solution, Visual Studio doesn't prompt to install required workloads. Adding a .vsconfig file makes VS detect missing components and offer to install them.

Includes: .NET desktop workload, .NET 9 SDK/runtime, and Windows 11 SDK (26100), matching what the template project requires.

PR Checklist

Includes the workloads and components needed to build the CmdPal
extension template: .NET desktop, .NET 9 SDK/runtime, and the
Windows 11 SDK (26100). Visual Studio will prompt to install
missing components when the solution is opened.

Fixes microsoft#39114
@michaeljolley michaeljolley added the Product-Command Palette Refers to the Command Palette utility label Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Product-Command Palette Refers to the Command Palette utility

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CmdPal: We need to add a .vsconfig to the template (was: Creating Custom Extension - Unable to debug/launch)

2 participants