Think alternatives for VS2015

[jgsogo]

Current efforts trying to make the extension compatible with VS2015 have arrived at a dead-end. There is an incompatibility regarding VCProjectEngine.dll for different versions of the library that is shipped with different versions of Visual Studio and the casting from Project.object to VCProject fails for one version or the other.

Here there are some useful links that are interesting to read: #75 (comment)

I'm opening this issue to think about alternatives and decide the roadmap for it.

Thanks

[jgsogo]

Some ideas that come to my mind:

• Keeping current implementation:
  • Create two different extensions, both could have the same source, but different dependencies.
  • Create two different .dll, one for each incompatible VS version and load one of them dynamically from a third DLL (the one that is actually loaded by VS) depending on the VS version. All these DLLs should be packed inside the same vsix so we keep just one extension in the marketplace
• Change implementation: the incompatibility arises because we are trying to cast an object to VCProject to retrieve its properties (configuration values like toolset, runtime,...). We might we able to retrieve these properties using the original Project object.

Please, suggest your ideas, all of them will be more than welcome.

[solvingj]

Consider raising this issue in gitter.com/extendvs which is the best channel for community developers working on VS Extensions. Maybe others there have experience with this.

[lasote]

If changing the implementation to avoid the cast to VCProject is a possibility I see it as the less problematic and easy to maintain way. But I assume, if you have open this issue and not just fixed it, that it is not that easy.

[SSE4]

@solvingj for me gitter.com/extendvs redirects to the http://www.goinfotek.com/ which seems to be something unrelated

[jgsogo]

Check this url: https://gitter.im/Microsoft/extendvs, I've already asked there, but without success.