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

Set-MsBuildDevEnvironment does not work if VsSetup is already installed #1575

New Issue
Closed
opened 2026-01-30 22:30:57 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 22:30:57 +00:00
Owner
Copy Link

Originally created by @adiviness on GitHub (Jun 9, 2019).

Originally assigned to: @DHowett-MSFT on GitHub.

Steps to reproduce

open up powershell, import-module on openconsole.psm1. Run Set-MsBuildDevEnvironment. It'll download VsSetup as a local module and import it. run powershell -noprofile and import openconsole.psm1 again, then run SetMsBuildDevEnvironment. It'll fail to find the path to VsSetup with error:

Get-ChildItem : Cannot find path 'C:\Users\austi\Documents\oss\terminal\tools\2.2.5' because it does not exist.
At C:\Users\austi\Documents\oss\terminal\tools\OpenConsole.psm1:44 char:9
+         Get-ChildItem -Path $versions[0] "$Name.psd1" | Import-Module
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\Users\austi\...nal\tools\2.2.5:String) [Get-ChildItem], ItemNotFound
   Exception
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

Expected behavior

Setting up build tools should work

Actual behavior

error finding local module.

It looks like a pathing problem on the last line of Set-MsBuildDevEnvironment:

Get-ChildItem -Path $versions[0] "$Name.psd1" | Import-Module

Originally created by @adiviness on GitHub (Jun 9, 2019). Originally assigned to: @DHowett-MSFT on GitHub. <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Steps to reproduce open up powershell, `import-module` on openconsole.psm1. Run `Set-MsBuildDevEnvironment`. It'll download VsSetup as a local module and import it. run `powershell -noprofile` and import openconsole.psm1 again, then run `SetMsBuildDevEnvironment`. It'll fail to find the path to VsSetup with error: ``` Get-ChildItem : Cannot find path 'C:\Users\austi\Documents\oss\terminal\tools\2.2.5' because it does not exist. At C:\Users\austi\Documents\oss\terminal\tools\OpenConsole.psm1:44 char:9 + Get-ChildItem -Path $versions[0] "$Name.psd1" | Import-Module + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (C:\Users\austi\...nal\tools\2.2.5:String) [Get-ChildItem], ItemNotFound Exception + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand ``` # Expected behavior Setting up build tools should work # Actual behavior error finding local module. It looks like a pathing problem on the last line of `Set-MsBuildDevEnvironment`: `Get-ChildItem -Path $versions[0] "$Name.psd1" | Import-Module`
claunia commented 2026-01-30 22:30:58 +00:00
Author
Owner
Copy Link

@Arnatious commented on GitHub (Jun 19, 2019):

$versions = Get-ChildItem "$modules_root\$Name" | Sort-Object
When printed, versions shows the correct directory

λ  Write-Output $versions[0]


    Directory: C:\Users\arnat\Documents\Terminal\.PowershellModules\VSSetup


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        6/11/2019  10:40 PM                2.2.5

It looks like when $versions is passed as an argument to -Path it's converted to a string via $versions[0].ToString(), aka $versions[0].Name

Changing the call to Get-ChildItem -Path $versions[0].FullName "$Name.psd1" | Import-Module causes a different error

Import-Module : The specified module 'VSSetup.psm1' was not loaded because no valid module file was found in any
module directory.
At line:1 char:66
+ ... Item .\.PowershellModules\VSSetup\2.2.5\ VSSetup.psm1 | Import-Module
+                                                             ~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (VSSetup.psm1:String) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

Wrapping that call in (...).FullName as well produces

New-Object : Cannot find type [Microsoft.VisualStudio.Setup.PowerShell.VersionTable]: verify that the assembly
containing this type is loaded.
At C:\Users\arnat\Documents\Terminal\.PowershellModules\VSSetup\2.2.5\VSSetup.psm1:5 char:6
+     (New-Object 'Microsoft.VisualStudio.Setup.PowerShell.VersionTable ...
+      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidType: (:) [New-Object], PSArgumentException
    + FullyQualifiedErrorId : TypeNotFound,Microsoft.PowerShell.Commands.NewObjectCommand
@Arnatious commented on GitHub (Jun 19, 2019): `$versions = Get-ChildItem "$modules_root\$Name" | Sort-Object` When printed, versions shows the correct directory ``` λ Write-Output $versions[0] Directory: C:\Users\arnat\Documents\Terminal\.PowershellModules\VSSetup Mode LastWriteTime Length Name ---- ------------- ------ ---- d----- 6/11/2019 10:40 PM 2.2.5 ``` It looks like when $versions is passed as an argument to -Path it's converted to a string via `$versions[0].ToString()`, aka `$versions[0].Name` Changing the call to `Get-ChildItem -Path $versions[0].FullName "$Name.psd1" | Import-Module` causes a different error ``` Import-Module : The specified module 'VSSetup.psm1' was not loaded because no valid module file was found in any module directory. At line:1 char:66 + ... Item .\.PowershellModules\VSSetup\2.2.5\ VSSetup.psm1 | Import-Module + ~~~~~~~~~~~~~ + CategoryInfo : ResourceUnavailable: (VSSetup.psm1:String) [Import-Module], FileNotFoundException + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand ``` Wrapping that call in `(...).FullName` as well produces ``` New-Object : Cannot find type [Microsoft.VisualStudio.Setup.PowerShell.VersionTable]: verify that the assembly containing this type is loaded. At C:\Users\arnat\Documents\Terminal\.PowershellModules\VSSetup\2.2.5\VSSetup.psm1:5 char:6 + (New-Object 'Microsoft.VisualStudio.Setup.PowerShell.VersionTable ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidType: (:) [New-Object], PSArgumentException + FullyQualifiedErrorId : TypeNotFound,Microsoft.PowerShell.Commands.NewObjectCommand ```
claunia commented 2026-01-30 22:30:58 +00:00
Author
Owner
Copy Link

@Arnatious commented on GitHub (Jun 19, 2019):

As a workaround, I manually ran

Install-Module VSSetup
Import-Module VSSetup

At this point, there were no errors running Set-MsbuildDevEnvironment

λ  Set-MsbuildDevEnvironment -v
VERBOSE: Searching for VC++ instances
VERBOSE: Setting up environment variables
@Arnatious commented on GitHub (Jun 19, 2019): As a workaround, I manually ran ``` Install-Module VSSetup Import-Module VSSetup ``` At this point, there were no errors running Set-MsbuildDevEnvironment ``` λ Set-MsbuildDevEnvironment -v VERBOSE: Searching for VC++ instances VERBOSE: Setting up environment variables ```
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 Area-Build Area-CodeHealth Issue-Bug Needs-Tag-Fix Product-Meta Resolution-Fix-Committed
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#1575
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?