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

Completely destroyed my VS 2022 installation #122

Closed
alexdresko opened this issue Jul 11, 2022 · 4 comments
Closed

Completely destroyed my VS 2022 installation #122

alexdresko opened this issue Jul 11, 2022 · 4 comments
Assignees
Milestone

Comments

@alexdresko
Copy link

I cannot load VS without getting a ton of errors after installing this plugin. I will probably have to reset VS to defaults in order to get any work done today. I do not have time to troubleshoot this, but I figured it was worth creating an issue so others might know of the danger.

@alexdresko alexdresko changed the title Completely destroyed my VS installation Completely destroyed my VS 2022 installation Jul 11, 2022
@jgo-bvb
Copy link

jgo-bvb commented Jul 25, 2022

Probably #120 @alexdresko ? Just uninstall the extension and you should be fine

@StefanKert
Copy link
Owner

Hi @alexdresko,

thank you very much for reaching out and sorry for the inconvenience caused. As @jgo-bvb posted, I do hope that uninstalling the extension helped resolving this issue. As I am not sure yet if this is a duplicate of #120 I'll keep this issue open.

If you have got a ActivityLog of the crash I can do further checks @alexdresko

@StefanKert
Copy link
Owner

Hi there,

a Preview of version 4.x is available in the VSIX Gallery feed. You can follow along with the installation instructions from the README https://github.com/StefanKert/BuildVision?tab=readme-ov-file#setup-visual-studio-for-preview-channel. Would love to hear if this fixes the issues you are facing. As soon as the issues that people are currently seeing are resolved there will be a official marketplace release.

Thanks :)

@StefanKert StefanKert self-assigned this Apr 29, 2024
@StefanKert StefanKert added this to the v4.0.0 milestone Apr 29, 2024
@StefanKert
Copy link
Owner

Closing this issue since currently it is a bit hard to follow along with the different issues / states. If you still see issues with the latest 4.0 please create another one. Thank you very much :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants