Remove Visualizer Menu from Visual Studio - visual-studio-2017

I installed an extension for Visual Studio 2017, but it has left the menus behind.
[
Does anyone know how to remove these as the author is not responding.
Any help would be great, thanks in advance
Andrew

Does the author upload it to github as an open source project? You can modify the code to disable it then rebuild and install it.
If not, you can only wait for the author's response.

Sorry, I should have posted back that you can remove it from {documents}\Visual Studio 20xx\Visualizers\ folder.
Thanks for the reply and sorry to have wasted your time.

Related

The setup for this installation of visual studio is not complete, really?

I have been using Vs 2017 for several months on dev machine. This fine morning says setup incomplete. Am I missing something?
In this case you need to go to Control Panel => Programs and Features and choose Visual Studio and update it.
VS 2017 (15.6.6) was fine for me on Friday 6/1/18 on Windows 10, but same issue as OP today after a restart.
As suggested by the dialog and Retired Ninja, I ran the Visual Studio Installer (to 15.7.3 after updating VS Installer) and that fixed it.
Note that the 15.7.3 update was a 7.73 GB download. Your download size may vary.
This has happened to me for the last 3 upgrades in Visual Studio Enterprise 2017 (now again on upgrade to 15.9.21).
The fastest fix (and I'm not sure why) is simple and doesn't bomb your settings or take for ever.
In the Visual Studio Installer, click on Modify.
Click "Modify" on the bottom right corner.
Yes it says "Total space required 0 KB".
Yes you didn't really change anything.
It will then act like it is downloading something. (not sure what)
It will then act like it is installing something. (again, not sure what)
Open Visual Studio 2017 and it works.
Hope this helps.
If you have an offline installation like me and can't simply re-run the Visual Studio Installer you can edit devenv.isolation.ini and change the last line to read SetupFinished=true. It will detect your trickery and complain, but at least it will launch again.
Edit: I ended up getting the Visual Studio Installer to fix the issue after choosing the "Download then Install" option. Maybe I was too impatient when I initially stopped the update? My above answer is useful when you need to get work done that isn't affected by the broken features, but you will likely encounter problems later on.
just had the same problem (without any reason with) vs 2019 prof, after googling and reading on that topic, just went to vsix, looked for some individual component to install/uninstall, randomly picked cloud explorer, uninstalled it and some dependent components and VS 2019 prof started normally
decided to leave this here. may be it helps somebody
Solved: I did following steps, run the visual studio and it works for me.
In my case visual studio was working fine , I just restarted the PC, this popup was keep coming when I try to open visual studio.(in my case I was using VS 2019)
Go to this path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE"
Open devenv.isolation.ini, set SetupFinished=true and save.
Now open visual studio.
Cheers!
In my case did following steps:
Clear temp files (you can %temp% in run command and Shift+Delete files)
Restart your computer
Open visual studio it will work properly.
Update: Faced problem again after couple of days, This time I go to C:\Program Files (x86)\Microsoft Visual Studio\Installer.
Click on retry.
Select one more feature which I had already installed on my Visual Studio
Click on modified and after installation it worked again.
This happened to me after I canceled a plugin update.
I solved by going to this site that has the latest update of Visual Studio.
https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes
I downloaded and upgraded it.
After that, Visual Studio worked.
If your VS is already upgraded, there´s an option to "repair" on the installer.
For this problem, goto uninstall screen in control panel right-click visual studio and select option change, Installer page will open now, In that window without changing anything click modify. it will solve the problem. I'm using VS Professional 2017
I got the same error today morning. This is what I did:
I ran the visual studio installer then I clicked on Modify.
The installer was showing 0KB Required. I continued and then it downloaded and installed. (Not sure what).
After that installation, it was able to launch.
I hope it works for you as well.
I was using Vs 2019 professional 16.6 and happened to me this issue one morning. I modified the installation by adding Azure Development tools even though I was not using it. This fixed the issue.
I just updated to 15.9.24 and I got this yet again, as I have my resolution above, and Visual Studio 2019 seems to be a lot better with avoid this issue. The installer for 2019 you do have to change something and do the modification, 2017 you don't have to change anything.
I reported this issue through Developer Community:
Setup not complete since 15.9.21
I don't know why but sometimes its buggy
it's up to date but after launch visual studio this error prompted !
you have to click modify in vs installer and just modify it.
its not going to download anything.
after a moment launch vs and enjoy :)
For VS2022, WIN11:
Control Panel > Programs > Programs and Features > Microsoft Visual Studio Installer
Then, click on Change and resume the previous process.

Visual Studio 2017: A fatal error has occurred and debugging needs to be terminated

When executing unit tests in debugging mode, I get the following error message:
A fatal error has occurred and debugging needs to be terminated. For more
details please see the Microsoft Help and Support web site.
HRESULT=0x8000ffff. ErrorCode=0x0.
So my steps to fix the issue,
1- [Preventive action]
Update the Visual studio 2017 , from the yellow flag notification or from
Tools >> Extensions & Updates >> Updates >> visual studio marketplace.
2- Search in your test solution for launchsettings.json file and remove it.
3- Clean the test solution .
4- Rebuild the project .
5- Make a cup of coffee ;).
Restarting Visual Studio solved this issue for me.
Cleaning the solution didn't work for me, and I couldn't find a launchsettings.json.
What eliminated the error for me: Changing the Startup project to a project other than the test project, as mentioned in this MSDN forum post.
Solution
Clean the solution and try again. See Visual Studio Forum for details. It helped in my case.
Try to check your depencency packages and references and try to ensure that all is ok. I fix this problem delete unnecessary and broke dependencies.
I had a similar issue and was because of the .Net Framework Target settings were wrong. It was set to .NET 5.0 which was not supported by VS2017. Opening the project in VS2019 solved the issue.

Error message 'Value cannot be null. Parameter name: userContext' in Visual Studio 2017

I get error message
'Value cannot be null. Parameter name: userContext'
in Visual Studio 2017 when trying to click notification or opening Extensions and updates from tools folder.
Before answering can you look this Answer. The answer did not work on me.
I had same problem to. My solution is quite similar from Tahir Hassan.
Go to ...AppData\Local\Microsoft\VisualStudio\15.0...\ delete the file "privateregistry.user.bin"
Start Visual Studio -> VS only ask to sign in or not.
You don't have to download any updates after that.
I had this problem. Close VS, go to %LOCALAPPDATA%\Microsoft\VisualStudio\ and delete/rename a folder whose name starts with 15.0_.
Then start Visual Studio, then download and install the latest update.
After that it should work - Best of luck.
I had a similar issue with Visual Studio 2022. I would perform Ctrl + F and it would simply give me a message box saying:
Value cannot be null. Parameter name: textView.
Simply closing and reopening Visual Studio worked to resolve this, if anyone is experiencing this issue.

Visual Studio 2017 Solution Explorer is empty

When I open an existing VS2015 solution file in VS2017, Solution Explorer is empty. I've tried to close and reopen Visual Studio several times, but the same thing happens every time. How to fix this?
This should fix it:
Close Visual Studio
Open Developer Command Prompt for VS 2017 (from Windows start menu)
Run devenv /updateconfiguration
Reopen Visual Studio
I'm experiencing the same issue. VS goes through all the steps when loading a solution, including "Preparing Solution", but then the Solution Explorer just comes up empty. So far I haven't found a solution. I tried deleting .suo files, and I tried cleaning the solution.
Like Eivind, I need to open the solution from the file menu. Fortunately, that has always worked for me so far.
Today's update for VS2017 fixed it for me. Also see https://developercommunity.visualstudio.com/content/problem/24529/solution-doesnt-open-in-vs-2017.html
I faced this type of issue when opening project on visual studio 2017.
If you have connected with TFS and I believed that your connection has been lost.
Re-connect and close the project and then reopen using visual studio.
Hope this will helpfull!
On the Notification Area there is a message for Visual Studio 2017 updates. Click on that and this fixed my problem of empty Solution Explorer when u click on a 2015 sln file.

silent closing VS 2008 on Windows 7

I am trying to build a MFC Windows Application with Visual Studio 2008 on Windows 7. I use the "Batch build" feature of Visual Studio to get both Release and Debug of several projects' outputs with only one-click.
The problem is: Frequently, after I instruct VS 2008, some minutes later VS closes its window without any explanation. I have already seach the Web about these things and it seems that nobody as an answer.
I cannot be more specific than this. VS simply closes and you will not get any information.
Thanks in advance,
Sérgio
The best answer I could give would be to contact Microsoft directly and let them know of your problem. If there is no error information, it could be that they are not handling an exception and the program is just closing instead.
Seems that installing the patch quoted on http://arstechnica.com/microsoft/news/2009/03/widely-reported-crash-in-visual-studio-2008-sp1-fixed.ars solves the issue.