You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 21, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 21, 2023. It is now read-only.
Experimental extension throws exceptions when normal version is installed #2006
The GitHub for Visual Studio extension installs with the AllUsers option set to true. As well as installing for all users, this option will make the extension appear in all instances of Visual Studio (regular and Experimental).
When the extension is installed and launched from Visual Studio, the version in development will be installed into the Experimental instance. Most, but not quite all configuration from the AllUsers extension will be overridden by the version in development. Enough of the AllUsers version is left behind to cause confusing exceptions when the UI loads.
The most likely problem is that a BindingPath from the AllUsers version is still active (pointing to the extension under c:\Program Files (x86)\...). This can cause a mixture of assemblies from both version to be loaded. Another potential issue is when a package is removed from the version in development. Rather than disabling the package, the package from the AllUsers will be loaded instead.
How to fix
We need to prevent the AllUsers extension from installing itself in the Experimental instance. The fix is different in Visual Studio 2017 and 2015.
For Visual Studio 2017
On Visual Studio 2017 we need to uninstall the experimental extension and disable the AllUsers extension.
Start Experimental Instance of Visual Studio 2017
Using Tools > Extensions and Updates..., find GitHub for Visual Studio and select Uninstall
Close all instances of Visual Studio
Find the VSIX Installer dialog and select Modify
Start Experimental Instance of Visual Studio 2017
Using Tools > Extensions and Updates..., find GitHub for Visual Studio and select Disable (not Revert)
Close Visual Studio
Open GitHub for Visual Studio solution in Visual Studio 2017
Right-click on GitHub.VisualStudio and Rebuild (don't skip this step!)
Install and launch extension (F5)
Check that warning dialog doesn't appear and extension is working
For Visual Studio 2015
On Visual Studio 2015 we need to uninstall the experimental extension and then uninstall the AllUsers extension.
Start Experimental Instance of Visual Studio 2015
Using Tools > Extensions and Updates..., find GitHub for Visual Studio and select Uninstall
Click the Restart now button at the bottom
Wait for Experimental Instance to restart
Using Tools > Extensions and Updates..., find GitHub for Visual Studio and select Uninstall
Close Visual Studio
Open GitHub for Visual Studio solution in Visual Studio 2015
Right-click on GitHub.VisualStudio and Rebuild (don't skip this step!)
Install and launch extension (F5)
Check that warning dialog doesn't appear and extension is working
NOTE: If you want to use the extension on your regular Visual Studio 2015 instance, install it using the DogfoodVsix extension. This will install for the current user only and won't impact the Experimental instance.
changed the title [-]Developing extension with GitHub for Visual Studio installed in default instance[/-][+]Experimental extension throws exceptions when normal version is installed[/+]on Oct 22, 2018
Activity
[-]Developing extension with GitHub for Visual Studio installed in default instance[/-][+]Experimental extension throws exceptions when normal version is installed[/+]Open issue with how to fix