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

Adding Visual Studio Developer Tools - Incorrect paths #16824

New Issue
Open
opened 2026-01-31 05:24:07 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:24:07 +00:00
Owner
Copy Link

Originally created by @fdacumos on GitHub (Feb 18, 2022).

Windows Terminal version

1.12.10334.0

Windows build number

10.0.19042.0

Other Software

Visual Studio 2019
Visaul Studio 2022

Steps to reproduce

  1. Install Visual Studio 2019
  2. Install Windows Terminal
  3. During the install, choose to add the Visual Studio Developer Tools as a Profile (Developer PowerShell for VS 2019)
  4. Install Visual Studio 2022
  5. Attempt to open up the "Developer PowerShell for VS 2019" WT Profile

Expected Behavior

When going to Windows Terminal, I should be able to open up my VS 2019 Developer Prompt by selecting "Developer PowerShell for VS 2019". However, it errors out and the icon is also missing.

Actual Behavior

I get the error:

Import-Module: Assembly with same name is already loaded
Enter-VsDevShell: Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'VsInstallPath'. Specified method is not supported.

Reasons:
The Problem is with the Windows Terminal Profile settings. For that WT Profile, under commandLine it shows:

"commandline": "C:\\Program Files\\PowerShell\\7\\pwsh.exe -noe -c \"&{$vsPath = &(Join-Path ${env:ProgramFiles(x86)} '\\Microsoft Visual Studio\\Installer\\vswhere.exe') -property installationpath; Import-Module (Join-Path $vsPath 'Common7\\Tools\\Microsoft.VisualStudio.DevShell.dll'); Enter-VsDevShell -VsInstallPath $vsPath -SkipAutomaticLocation}\"; cd ~",

If you have multiple versions of Visual Studio installed, the vswhere.exe will return an Array of items, so the PowerShell to register is incorrect. It needs to reference the first element of the $vsPath variable. This can be manually fixed by editing the settings and changing the line to:

"commandline": "C:\\Program Files\\PowerShell\\7\\pwsh.exe -noe -c \"&{$vsPath = &(Join-Path ${env:ProgramFiles(x86)} '\\Microsoft Visual Studio\\Installer\\vswhere.exe') -property installationpath; Import-Module (Join-Path $vsPath[0] 'Common7\\Tools\\Microsoft.VisualStudio.DevShell.dll'); Enter-VsDevShell -VsInstallPath $vsPath[0] -SkipAutomaticLocation}\"; cd ~",

Missing Icon
Also, for the missing Icon, the default install references the Icon under the Visual Studio "Enterprise".

"%ProgramFiles(x86)%\\Microsoft Visual Studio\\2019\\Enterprise\\Common7\\IDE\\Assets\\VisualStudio.70x70.contrast-standard_scale-180.png",

If you have Visual Studio "Professional" installed, the icon will break. Simply fix this by changing the line to:

"%ProgramFiles(x86)%\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\Assets\\VisualStudio.70x70.contrast-standard_scale-180.png",
Originally created by @fdacumos on GitHub (Feb 18, 2022). ### Windows Terminal version 1.12.10334.0 ### Windows build number 10.0.19042.0 ### Other Software Visual Studio 2019 Visaul Studio 2022 ### Steps to reproduce 1. Install Visual Studio 2019 2. Install Windows Terminal 3. During the install, choose to add the Visual Studio Developer Tools as a Profile (Developer PowerShell for VS 2019) 4. Install Visual Studio 2022 5. Attempt to open up the "Developer PowerShell for VS 2019" WT Profile ### Expected Behavior When going to Windows Terminal, I should be able to open up my VS 2019 Developer Prompt by selecting "Developer PowerShell for VS 2019". However, it errors out and the icon is also missing. ### Actual Behavior I get the error: ``` Import-Module: Assembly with same name is already loaded Enter-VsDevShell: Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'VsInstallPath'. Specified method is not supported. ``` Reasons: The Problem is with the Windows Terminal Profile settings. For that WT Profile, under commandLine it shows: ``` "commandline": "C:\\Program Files\\PowerShell\\7\\pwsh.exe -noe -c \"&{$vsPath = &(Join-Path ${env:ProgramFiles(x86)} '\\Microsoft Visual Studio\\Installer\\vswhere.exe') -property installationpath; Import-Module (Join-Path $vsPath 'Common7\\Tools\\Microsoft.VisualStudio.DevShell.dll'); Enter-VsDevShell -VsInstallPath $vsPath -SkipAutomaticLocation}\"; cd ~", ``` If you have multiple versions of Visual Studio installed, the `vswhere.exe` will return an Array of items, so the PowerShell to register is incorrect. It needs to reference the first element of the `$vsPath` variable. This can be manually fixed by editing the settings and changing the line to: ``` "commandline": "C:\\Program Files\\PowerShell\\7\\pwsh.exe -noe -c \"&{$vsPath = &(Join-Path ${env:ProgramFiles(x86)} '\\Microsoft Visual Studio\\Installer\\vswhere.exe') -property installationpath; Import-Module (Join-Path $vsPath[0] 'Common7\\Tools\\Microsoft.VisualStudio.DevShell.dll'); Enter-VsDevShell -VsInstallPath $vsPath[0] -SkipAutomaticLocation}\"; cd ~", ``` **Missing Icon** Also, for the missing Icon, the default install references the Icon under the Visual Studio "Enterprise". ``` "%ProgramFiles(x86)%\\Microsoft Visual Studio\\2019\\Enterprise\\Common7\\IDE\\Assets\\VisualStudio.70x70.contrast-standard_scale-180.png", ``` If you have Visual Studio "Professional" installed, the icon will break. Simply fix this by changing the line to: ``` "%ProgramFiles(x86)%\\Microsoft Visual Studio\\2019\\Professional\\Common7\\IDE\\Assets\\VisualStudio.70x70.contrast-standard_scale-180.png", ```
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-Bug Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#16824
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?