Support for Visual Studio 2015
DNX support will be introduced as this platform stabilises. Although VS2015 is in an RC state now, DNX/ASPNET5 is still very much in beta and is still undergoing very heavy internal changes. I recommend steering away from this platform until Microsoft have 'finished' it.
Damian Hickey commented
Support for dnx projects (born from the aspnet vnext effort) will be necessary too.
I've got some news one this one :)
The above build contains an installer that targets VS2015. It should also work with the new language features.
I appreciate you looking into it and look forward to the next version, now I just have to see if I can convince my coworkers to forgo all the new language features.
Unfortunately, there's no way to force NCrunch to use a different version of MSBuild. NCrunch interacts with MSBuild through the MSBuild API, which is statically referenced by nCrunch.VSIntegration* DLLs.
Sorry, it will need to be a codefix to the program itself. I don't doubt that there will also be other things that need to be further adjusted to add support for VS2015.
I think that if we could get NCrunch to use the version of msbuild that ships with 2015 everything would work fine. I tried changing the assembly binding redirects in the nCrunch.TaskRunner*.config to point to the 14.000 version of the msbuild dlls with no perceptible effect. How does nCrunch determine the MsBuild.exe path when it's building?
At the moment the NCrunch engine is undergoing some major internal upgrades in preparation for VS2015 support.
NCrunch's official support for VS2015 is expected to be introduced when VS2015 is in beta. At time of writing this, VS2015 is in an advanced preview state.
I've heard a number of people comment that it is possible to make the current version of NCrunch work on the VS2015 preview by taking the VS2013 version and performing a manual installation into the VS2015 directory. Results of this seem to be hit and miss, and I can't guarantee that NCrunch will load using this method or that all features will work correctly. VS2015 does contain a number of new features which the existing version of NCrunch does not yet have consideration for (such as the new version of C#/Roslyn). If NCrunch is critical for your development I recommend holding back until VS2015 hits beta and support can be properly finalised with full regression testing etc.
With that said, I appreciate any efforts people make to report problems here that they encounter with using the VS2013 version of NCrunch in VS2015, as knowledge of these problems will be of definite value in testing and development for VS2015.
none of the c# 6 language features seem to be supported. NCrunch can't build the projects that use any of the new language features like the Null-Conditional Operator.
Benjamin Nitschke commented
Current workaround is to copy the VS2013 files manually as described here: http://forum.ncrunch.net/yaf_postst1360_NCrunch-for-Visual-Studio-14.aspx