Software solutions for a mobile world

Preparing for a presentation on Visual Studio Extensions, I have done a lot of testing of my test application to make sure everything goes smoothly. 

When you are testing your extension, it fires up the 'experimental' version of VS2022 as denoted by the 'EXP' in the title.

 Every time you add a different extension, even with the same name, by default it gets added to the 'Tools' menu. It can finish up looking like this:-

As you can see, there is a mess of 5 new commands, with duplication. Tried uninstalling the extensions in VS2022, but after a few seconds, I got the Visual Studio Is Busy message. I tried searching for a solution and saw various convoluted suggestions to remove them. I did a search on my Windows 11 task bar for Visual Studio 2022 and saw a command line option - Reset the Visual Studio Experimental Instance


This is a shortcut to 

%comspec% /C "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VSSDK\VisualStudioIntegration\Tools\Bin\CreateExpInstance.exe" /Reset /VSInstance=17.0_45ae9489 /RootSuffix=Exp && PAUSE

starting in %compec%

I ran this and then tested another add-in. The reset took my back to 'dark mode' , so I changed to 'normal' mode, re-ran the test and saw:-

Result!! I was back to just seeing the one I tested. The shortcuts to resetting and starting the experimental instances are in the 'Start Menu'. 


M: +44 (0)7860 907493




Twitter Feed