Re-add support for VS2017
Opened this issue · 1 comments
pgenfer commented
There were some changes in the VS Gallery/Marketplace:
Extensions which want to support VS 2017 also have to be build with the VS 2017 extension toolkit (which is part of VS2017 RC), and it seems that also the vsix project files have to be migrated.
The goal is to build the mixinSharp extension with the new extension toolkit and check if it can still be used/opened with VS 2015.
Also update the AppVeyor build CI projecss by using a VS 2017 image
pgenfer commented
Problem seems to be a bit more difficult:
- Looks like the new vsix projects are not downward compatible, so adding support for VS 2017 would require two separate vsix projects.
- Opening the mixinSharp library project currently crashes the VS 2017 RC (object reference not set to an instance of an object when opening the project), so maybe the library project has to be set up from scratch to support VS 2017