Visual Studio 2017 support

[maleet]

As this is launched now, will there be extension available?

[urasandesu]

Currently, Prig has not supported Visual Studio 2017 yet, sorry.

I'm going to release next version this week end, but it will contain only some bug fixes.

Supporting Visual Studio 2017 is after that.

[bp2008]

Also interested in this update!

Great work so far.

[urasandesu]

MEMO
Visual Studio 2017 also uses vstest.executionengine as same as the previous version to run tests. So we supposed that we just change VSIX manifest to correspond this issue originally. However, it turned out that there are two issues as follows:

• VSIX manifest has been upgraded to v3 in Visual Studio 2017.
  Until now, it was v2. The manifest cannot handle by Visual Studio 2013 we currently use.
• So we need to upgrade Visual Studio to 2017 but some middlewares have not supported it yet.
  For example, Boost C++ Libraries only support until Visual C++ 14.0. I tried to build it by Visual Studio 2017, but it couldn't.

We will begin to fix this issue after the above issues are all solved.

[urasandesu]

MEMO
I found the VSIX installer of Visual Studio 2017 reducing function. In addition, Visual Studio 2017 has many problems for VSIX currently. We should review the plan to support VS2017.

[urasandesu]

MEMO
In Visual Studio 2017, I found a critical bug in the API that Prig uses. We interrupt the work for supporting Visual Studio 2017 until this issue is corrected.

[urasandesu]

MEMO
The critical bug that I found was fixed at version 15.2(26430.6)! 😆

However, I haven't confirmed whether the integration tests can run all combination because of another issue. Please wait a little while more... 😢

[urasandesu]

MEMO

Today, Visual Studio 2017 version 15.3(26730.3) is released. But the issue is continuing to reproduce. Developer Community is noncooperative. I don't know what I should do... 😞

[Mardoxx]

Post an issue on vstest repo https://github.com/Microsoft/vstest someone may be able to point you to someone who can help!

[urasandesu]

@Mardoxx, thank you for your advice!
I reported the issue as microsoft/vstest#999.

[urasandesu]

MEMO

Sushil Baid (MSFT) told me the workaround for the issue! I'm going to resume the work that is to support Visual Studio 2017 by adopting the workaround.

[Mardoxx]

@urasandesu Very nice, thank you!

[bp2008]

Great news 👍

[antonioaversa]

Great to see that we'll have soon Prig working in VS 2017!
That will allow me to use it at work.

Thanks for your work!