- Home /
- Visual Studio /
This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more
Get help from our community supported forum
Report an issue
in Visual Studio Installer or Visual Studio
This allows diagnostic information about the program to be included in your report
1. Installer or Visual Studio
2. Report a Problem
3. Type and Submit
Available on Visual Studio 2017, Installer, and newer releases
Would you like to know more?
A Visual Studio 2017 extension installed by the VSIX installer is incorrectly disabled after installation
Using Visual Studio 2017, create an empty VSIX project using File / New / Project / Templates / Visual C# / Extensibility / VSIX Project. Hit Build. Close Visual Studio, then install the extension by double-clicking the VSIX file in the bin\Debug folder. Start Visual Studio 2017, go to Extensions and Updates, and see that the extension is installed but disabled. It should be enabled.
This is a breakage in Visual Studio 2017 - if you follow those same steps using Visual Studio 2015, the extension is correctly enabled after restarting Visual Studio 2015.
Note that in both cases the extension is being installed by the VSIX installer, not by an external installer, and in both cases, InstalledByMsi is false.
I am getting a very similar behavior installing my package. This is my experience. After installation, I start VS, but the package does not appear in the list of installed extensions. If I close VS and reopen it, the package does appear in the list, but is disabled. After enabling the package and restarting VS again, the package is finally active. By the way, using the experimantal instance appears to work fine.
139 People are following this
