Closed ibuchanan closed 11 years ago
I think it just requires removing 12 (which is actually 2013) from the file:
From
<Installation>
<InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[11.0, 12.0)" />
<InstallationTarget Version="[11.0,12.0)" Id="Microsoft.VisualStudio.Premium" />
</Installation>
To
<Installation>
<InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[11.0)" />
<InstallationTarget Version="[11.0)" Id="Microsoft.VisualStudio.Premium" />
</Installation>
There are Chocolatey packages for 2013 now: http://chocolatey.org/packages?q=visual+studio+2013, and it verifies that "12.x" is 2013.
The range already means: at least 11.0 (VS2012) and up to, but not including, 12.0 (VS2013). So the range already meant just VS2012. Marking as worksforme.
As a potential user of the VS Client, I don't want VS Client to install into VS2013 so that I don't have to be frustrated when support tells me it's unsupported.
The vsixmanifest file still includes VS2013 (version 12) when the user docs don't include it as a supported version.
Acceptance Criteria: