Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashes when no MSFT_VSInstance class in WMI can be found #18

Closed
Hefaistos68 opened this issue Oct 11, 2023 · 0 comments
Closed

Crashes when no MSFT_VSInstance class in WMI can be found #18

Hefaistos68 opened this issue Oct 11, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@Hefaistos68
Copy link
Owner

For some unknown reason, the MSFT_VSInstance class may not exist in the WMI catalog. VSLauncherX crashes when this happens.

@Hefaistos68 Hefaistos68 added the bug Something isn't working label Oct 11, 2023
Hefaistos68 added a commit that referenced this issue Oct 13, 2023
…oft is using since 10/2023.

Now discovery tries the original WMI namespace, the new namespace and finally the Setup API.
Improvement on #18
Hefaistos68 added a commit that referenced this issue Oct 17, 2023
* Updated discovery of VS instances to use the new WMI namespace Microsoft is using since 10/2023.
Now discovery tries the original WMI namespace, the new namespace and finally the Setup API.
Improvement on #18

* Added continuous GIT status updates
Added VS activity log access through a button
Hefaistos68 added a commit that referenced this issue Oct 18, 2023
* Updated discovery of VS instances to use the new WMI namespace Microsoft is using since 10/2023.
Now discovery tries the original WMI namespace, the new namespace and finally the Setup API.
Improvement on #18

* Added continuous GIT status updates
Added VS activity log access through a button

* Small fix for when starting as admin or elevated already to avoid restarting through taskscheduler

---------

Co-authored-by: Andreas Saurwein <[email protected]>
Hefaistos68 added a commit that referenced this issue Apr 15, 2024
* Updated discovery of VS instances to use the new WMI namespace Microsoft is using since 10/2023.
Now discovery tries the original WMI namespace, the new namespace and finally the Setup API.
Improvement on #18

* Added continuous GIT status updates
Added VS activity log access through a button

* updated screenshot

* added exception handling for TaskBar in Win11
updated some packages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant