Reputation: 3120
I have created a VS2013 extension and now I want to install it in VS2012 as well. I read that I should edit the vsixmanifest and add the InstallationTarget, so I did. I have VS2102 Premium and VS2013 Ultimate installed. Here is the xml I added to the manifest:
<Installation InstalledByMsi="false">
<InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[11.0,12.0)" />
<InstallationTarget Id="Microsoft.VisualStudio.Premium" Version="[11.0,12.0)" />
</Installation>
Still, when I double click the vsix file to install it, it lists up just VS2013.
Upvotes: 2
Views: 651
Reputation: 26268
I just changed my VS2013 vsix to support VS2012 too, this is the resulted file:
<Installation InstalledByMsi="false">
<InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[12.0]" />
<InstallationTarget Version="[11.0,13.0)" Id="Microsoft.VisualStudio.Pro" />
</Installation>
If I opened my VS2013 vsix, it now supports
both of these.
I suspect if that doesn't work for you, you might suffer some weird cache anomaly from previous installations. You should confirm that it indeed does work for other fresh computers.
The other alternative I see that you're doing things in wrong order.
The correct order would be: modify the manifest (source.extension.manifest file) in visual studio, build the project. Once *.vsix file is produced, the manifest file has no longer any effect. The manifest is embedded in *.vsix file
Upvotes: 2