NCrunch for Visual Studio 14

Hi, thanks for posting!

At my last assessment, the CTP version of VS 14 didn't support side-by-side installation with VS 13, making it difficult to add support for this version without making some big changes to the NCrunch development environment. The CTP versions of VS historically tend to be quite different from their final release anyway, so much of the effort that goes into adding support for them is effectively wasted. As they are generally less stable, this also makes them harder to reliably integrate with and support.

Support will be added for VS vNext when it gets closer to its final release. Most likely when it is in a Beta or RC state.

Thank you, I see your points. I do however want to point out that I have them both installed side-by-side on my machine, without any problems. There are also Azure VMs available with VS 14 installed. As of CTP 3 I have not read anything suggesting that side-by-side installation is discouraged.

I've just used VS2013's manual installation on VS 14 CTP 3.
Test results, metrics and coverage markers all look fine on my solution 50 project solution running NUnit tests.
I needed to use VS 14 because VS 2013 has a bug that randomly breaks about 50% of builds.

Graham wrote:I've just used VS2013's manual installation on VS 14 CTP 3.
Test results, metrics and coverage markers all look fine on my solution 50 project solution running NUnit tests.
I needed to use VS 14 because VS 2013 has a bug that randomly breaks about 50% of builds.

That's great! Thanks for the early test on this. I do wish MS would fix that Resgen bug ... It's been driving me crazy for months. Do also make a point of sending any issues you find in VS14 through the bug reporter. I haven't yet had a chance to start adding support for it, but if you report problems you find then we can be sure to have them fixed before support becomes 'official'.

Graham wrote:I've just used VS2013's manual installation on VS 14 CTP 3.
Test results, metrics and coverage markers all look fine on my solution 50 project solution running NUnit tests.
I needed to use VS 14 because VS 2013 has a bug that randomly breaks about 50% of builds.

Thank you, that works just fine. (I was unaware of this simple way to get it working.)

I did get an error when running "devenv /setup" that said "The operation could not be completed.", but that doesn't seem to be an issue. Did you get that as well?

It took a long time (a minute or two) but I never had an error message, no.

For the VS 2015 preview I changed the Installation and Dependencies sections of the extension.vsixmanifest to this:

<Installation InstalledByMsi="false">
<InstallationTarget Version="[11.0,14.0]" Id="Microsoft.VisualStudio.Pro" />
<InstallationTarget Version="[11.0,14.0]" Id="Microsoft.VisualStudio.Premium" />
<InstallationTarget Version="[11.0,14.0]" Id="Microsoft.VisualStudio.Ultimate" />
</Installation>
<Dependencies>
<Dependency Id="Microsoft.Framework.NDP" DisplayName="Microsoft .NET Framework" Version="4.5" />
<Dependency Id="Microsoft.VisualStudio.MPF.12.0" DisplayName="Visual Studio MPF 12.0" Version="12.0" />
</Dependencies>

Looks good so far

Any Support for .kproj and project.json (new ASP.NET 5 Project Types) on the Horizon?

Der-Albert.com wrote:Any Support for .kproj and project.json (new ASP.NET 5 Project Types) on the Horizon?

No plans at the moment. I'll take a good look at this with the VS2015 integration to see what the options are :)

Is there a way to use the 2015 Build Tools? It seems not possible to use C# 6 feature without the new compiler.

Keep an eye out - there is an NCrunch build coming in the next few days that will work with this.

I've got some news one this one :)

http://blog.ncrunch.net/post/Engine-Separation-and-VS2015-Integration.aspx

The above build contains an installer that targets VS2015. It should also work with the new language features.

With Version with 2.11.10 seems not possible to Right-Click on a Cover Marker to Break oder Debug the covering Test.

It is possible to Right-Click, but the Test does not start. Also starting specific Test from the NCrunch Test Windows does not work.

In VS2015 and VS2013

2.11.10 had an ugly issue in the release build that broke a number of the UI options ... including the two you've described.

An update has been published to the blog page (2.11.12) including a fix for these issues. Try the build here and see if this solves things for you - http://blog.ncrunch.net/post/Engine-Separation-and-VS2015-Integration.aspx.

I believe 2.11.12 should be compatible with 2.11.10 grid nodes and settings files, so I hope it should just be an easy install over the top.

Yes, works. I only use local install.