Turns out in the light of advances in the vs2017 it doesn't make much sense to use the old installer.
New installer allows us to install into side-by-side versions of vs2017 (msbuild targets might be problematic, not sure if it's fixable) and automatically install prerequisite VS components. We also avoid changing the installer on every project change.
Only downside is that now VS2015 and VS2017 installer are different executables.
Should build now on appveyor, lightly tested.
Uninstallation might trigger this bug: https://developercommunity.visualstudio.com/content/problem/26008/vs-2017-rtm-vsixinstaller-cannot-find-setup-engine.html
Turns out in the light of advances in the vs2017 it doesn't make much sense to use the old installer. New installer allows us to install into side-by-side versions of vs2017 (msbuild targets might be problematic, not sure if it's fixable) and automatically install prerequisite VS components. We also avoid changing the installer on every project change. Only downside is that now VS2015 and VS2017 installer are different executables. Should build now on appveyor, lightly tested. Uninstallation might trigger this bug: https://developercommunity.visualstudio.com/content/problem/26008/vs-2017-rtm-vsixinstaller-cannot-find-setup-engine.html