The following extensions are not compatible with Visual Studio 2017 - reported by vxis extension

[janwilmans]

The message below can be seen when installing the visual studio forwarding extension in vs2017. The message can be safely ignored and fixing it would break compatibility with vs2010, which I'm unwilling to do right now.

We will fix this in a future version.

---------------------------
VSIX Installer
---------------------------
The following extensions are not compatible with Visual Studio 2017. Installation may cause Visual Studio to be unstable.

- CobaltFusion Output Window Forwarding

Do you want to continue?
---------------------------
Yes   No   
---------------------------

Workaround: just click 'yes' and it will install as usual

[janwilmans]

The fix would be to move to source.extension.vsixmanifest v3 and recompile the .vsix with an updated .vsix compiler. The vsixmanifest v3 is backwards compatible with vs2012 and up, but not with vs2010.

see http://www.visualstudioextensibility.com/2017/01/10/its-time-to-change-the-vsix-manifest-of-your-extension-to-v3-for-visual-studio-2017-compatibility/

[janwilmans]

maybe freeze a extension version and package two binaries, one frozen for 2010 and the latest of 2012 and up

[janwilmans]

I asked the author of VSColorOutput, Mike Ward to add this feature to his extension.

https://github.com/mike-ward/VSColorOutput/issues/77#issuecomment-414073352