- Home /
- Visual Studio /
Reported by Richie Hindle Dec 25, 2016 at 04:26 PM windows 10.0visual studio 2017 rc
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.
Added a solution by Matt Cavallari · Jun 21, 2017 at 04:33 PM
Thank you for filing this item with us, as we greatly appreciate the time spent. We are happy to inform you that this issue has been addressed and shipped in a subsequent release. Please go here for the latest release as well as information about included updates: https://www.visualstudio.com/vs/whatsnew/
Can't switch Git repo
1
Solution
ASP.NET SPA project
0
Solution
xproj and project.json not removed after migration
1
Solution
IDE0019 Inline temporary variable: Error with base type reference
0
Solution
XAML setting Style for a TextBox to a TextBlock => E_UNEXPECTED (0x8000FFFF)
0
Solution
VS Feedback and Installer appear layered on top of each other in the task bar
0
Solution
Intellisense is out of sync with build errors.
0
Solution
inline declaration causes compiler error
2
Solution
VSTS sync not working
0
Solution
Error on adding Runtime Text Template
0
Solution