starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Implement dynamic support for VSDevCmd profiles #14635

New Issue
Open
opened 2026-01-31 04:15:33 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:15:33 +00:00
Owner
Copy Link

Originally created by @heaths on GitHub (Jul 22, 2021).

I see a lot of developers adding entries to start the Visual Studio Developer Command Prompt, but its location can vary from machine to machine and multiple instances may be installed.

You can use the ISetupConfiguration COM server (the server is actually native, which is what we use in https://github.com/microsoft/vswhere) to find instances, which populate instances automatically if 1) installed, and 2) any instances are present.

A profile source could be something like VisualStudio_<InstanceId>. If the COM server can be created - ignoring REGDB_E_CLASSNOTREG - instances can be enumerated and command lines inferred from Common7\Tools\VSDevCmd.bat. As with any other dynamically discovered profile any number of profiles could be disabled.

The COM server supports Visual Studio 2017 and newer, but as with vswhere, older versions could be supported, though, IIRC, the actual batch file name and perhaps where it is located is different.

Originally created by @heaths on GitHub (Jul 22, 2021). I see a lot of developers adding entries to start the Visual Studio Developer Command Prompt, but its location can vary from machine to machine and multiple instances may be installed. You can use the [`ISetupConfiguration` COM server](https://docs.microsoft.com/dotnet/api/microsoft.visualstudio.setup.configuration.isetupconfiguration) (the server is actually native, which is what we use in https://github.com/microsoft/vswhere) to find instances, which populate instances automatically if 1) installed, and 2) any instances are present. A profile `source` could be something like `VisualStudio_<InstanceId>`. If the COM server can be created - ignoring `REGDB_E_CLASSNOTREG` - instances can be enumerated and command lines inferred from `Common7\Tools\VSDevCmd.bat`. As with any other dynamically discovered profile any number of profiles could be disabled. The COM server supports Visual Studio 2017 and newer, but [as with vswhere](https://github.com/microsoft/vswhere/blob/5d250b95a2c4d312961ed4e811fe240db197c404/src/vswhere.lib/InstanceSelector.cpp#L125-L142), older versions could be supported, though, IIRC, the actual batch file name and perhaps where it is located is different.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:15:33 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14635
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?