3F / vsSolutionBuildEvent

🎛 Event-Catcher with variety of advanced Actions to service projects, libraries, build processes, runtime environment of the Visual Studio, MSBuild Tools, and …
Other
79 stars 22 forks source link

This extension is not compatible with Visual Studio 15 and will not be supported in RC #36

Closed 3F closed 7 years ago

3F commented 8 years ago

My report here: https://developercommunity.visualstudio.com/content/problem/1180/index.html

It appeared in new 15 Preview 5 (25807.00) from the new extension format (not yet published documentation):

This extension is not compatible with Visual Studio 15 and will not be supported in RC. 
Installation may cause Visual Studio to be unstable.  Do you want to continue?

And mainly the Visual Studio Team is already thinking about compatible way, at least with previous VSIXv2 format.

Tim Sneath

Hi Denis Kuzmin, thanks so much for your feedback here. We haven't yet published documentation on the new extension format, but plan to do so within the next month.

We share your concern about avoiding breaking backwards compatibility. The challenge with the new modular architecture of Visual Studio is that the smallest install is now just a few hundreds of megabytes, and doesn't even include things like MSBuild. This enables us to support developers using languages like R or Python without imposing unnecessary components in their install.

So an extension like yours needs minor changes to the manifest to express the setup dependencies it actually needs. Our goal is to ensure that you can make these changes in a backwards-compatible way, at least as far as the previous VSIXv2 format.

Best wishes, Tim Sneath | Visual Studio Team

Denis Kuzmin

well, as you are can see the manifest is v1.0 for support all starting from VS2010: https://github.com/3F/vsSolutionBuildEvent/blob/master/vsSolutionBuildEvent/source.extension.vsixmanifest

i.e. if I correctly understand (https://msdn.microsoft.com/en-us/library/hh696828.aspx) the v2 is not supported by VS2010. Only VS2012, 2013, 2015

Therefore, should I finally stop support of VS2010 or provide 2 or 3 variant of my package for each version of Visual Studio ?!

or there are more ways ?

We still do not know about the final decision of the team (read my discussion here), but anyway I will consider support of VS2010 later

3F commented 7 years ago