Solution extensions file should define extensions per VS major version

[josundt]

When migrating from VS2019 to VS2022, it is hard to keep a common .vsext solution file with extension recommendations that will work for both VS versions in the transition period.

The .vsext JSON schema should be extended to have recommendations per VS major version, since (most) extensions target one major version only.

[loop8ack]

I have exact the same issue :/

But in my case, it's about team members who want to continue working with Visual Studio 2019.

[CZEMacLeod]

Or the extension should not prompt to install extensions that don't target the current version of VS running,

[astrohart]

I am working on this issue. I found a great piece of code on Stack Overflow here and I am adding properties to the Manifest class for the currently-running Visual Studio's Major, Minor, Build, and Revision version numbers.

Moreover, there will be a isVersionSpecific flag and a check box in the Export Extensions check box to turn version-specific behavior on or off. When off, the properties are all set to zero, and the import knows not to care what they are set to.

My two cents. I'll file a PR and see if Mads wants to imbibe it. I figure detailed VS version info in the .vsext file could potentially be of greater use down the road for certain applications, so while I was at it, I thought, 'why not?'