-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Switch to Get-VsSetupInstance in PowerShell Release Tool
* Requires `Install-Module VSSetup -Scope CurrentUser` to be run before using the release tool. * The latest version of Visual Studio 2022 removes the ability to find itself with WIM (the previous method)
- Loading branch information
1 parent
cacf197
commit af0e779
Showing
1 changed file
with
28 additions
and
28 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
af0e779
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@droidmonkey are you sure that using
$vs = Get-CimInstance MSFT_VSInstance -Namespace root/cimv2/vs
instead doesn't work? I don't think they removed the ability to find itself with WIM, it just that you have to explicitly specify the namespace. Made a PR here: #10101af0e779
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is 100% undocumented anywhere. Also if you dump the full WIMs class list, the VS one no longer is shown (although likely due to this namespace issue). In the future please write comments on the PR itself and not the commit.