I suggest you ...

Support .NET Core, .NET Standard (previously known as DNX) projects

Surprised this hasn't already been requested.

Going to be necessary to implement.

224 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Damian Hickey shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • AdminRemco Mulder (NCrunch Developer, NCrunch Website) commented  ·   ·  Flag as inappropriate

    @CB - An excellent question. VS2015 is built on top of the intermediate project.json system that VS2017 is set to replace completely. It's my understanding that MS have no intention of bringing the new .NET Core MSBuild system to VS2015, so it's reasonable to expect that NCrunch won't work with .NET Core under VS2015.

    From every angle, it looks like project.json is effectively dead from this point forwards. Xunit are abandoning it entirely. Jetbrains do still have integration with it, but I believe they are assessing their options. Because the project.json platform is so completely different from everything else, I expect we'll see considerable fragmentation in the ecosystem over the next few months as tool vendors and library authors move their products over and everything eventually settles on MSBuild.

    There are no plans for NCrunch to ever support project.json for .NET Core.

  • CB commented  ·   ·  Flag as inappropriate

    Remco - will there be support for VS2015 when VS2017 is released for NCrunch?

  • AdminRemco Mulder (NCrunch Developer, NCrunch Website) commented  ·   ·  Flag as inappropriate

    Progress Update: NCrunch is now able to create a .NET core test environment, execute test code and report results. I'm now working on getting the test frameworks integrated with the new environment and dealing with complex edge cases (i.e. distributed processing, test timeout enforcement, etc). The goal is to have a stable build of this ready before the official VS2017 release on the 7th of March.

  • AdminRemco Mulder (NCrunch Developer, NCrunch Website) commented  ·   ·  Flag as inappropriate

    Ok, rather than keep kicking up expected release dates for this feature and drowning in the collective pressure to deliver it, I'm going to put all my cards on the table and be as open and honest as I can be here.

    The releases of VS2017, MSTest V2, NUnit v3.6 and NCrunch V3 have between them raised a good number of support issues. Some of these issues are quite urgent. As important as .NET core support is, having a stable product will always be more important. People need to be able to pick up NCrunch and have it work as advertised.

    For this reason, v3.3 will be a fix-up release intended to address many of the above issues.

    v3.3 will also include some changes that are targeted towards .NET Core, such as the ability to recognise XML .NET Core projects, load them, and in some cases build them. Because none of these changes have been extensively tested they are likely to be unstable. As NCrunch doesn't yet have the capability to create a .NET Core runtime environment, the progress so far here isn't likely to be of much use to anyone yet.

    Further development of .NET Core support is the top priority for new development in NCrunch, but this will still be secondary to keeping NCrunch stable and up to date with the platforms and toolsets it is already tied into. Because of all the changes happening in the eco-system at the moment (especially around the VS2017 release), it is impossible to know what other tasks may need to be addressed between now and the release of .NET Core support. In turn, this makes any kind of accurate estimation of .NET Core support delivery timeframes impossible.

    So I ask everyone to please be patient and consider this uncertainty in your own planning. I would very much like to deliver this feature by next month, but I may very well not be able to.

  • AdminRemco Mulder (NCrunch Developer, NCrunch Website) commented  ·   ·  Flag as inappropriate

    My understanding MS are intending to have a tool to migrate the json based xproj files into the new stripped down csproj format.

    Working with the xproj files is a nightmare because they need a fully separate mechanism used to load and build them, which is baked into the .NET Core libraries with no extensibility options. So supporting this format really isn't feasible.

  • Sean Bennett commented  ·   ·  Flag as inappropriate

    Great to hear this is in progress! You'll get a number of customers back I'm sure :)

  • Joseph Musser commented  ·   ·  Flag as inappropriate

    I'm excited to see that you're working on VS2017 support, now that it's go-live! Are you still planning to start .NET Core support?

  • AdminRemco Mulder (NCrunch Developer, NCrunch Website) commented  ·   ·  Flag as inappropriate

    Joe Morris and David Carmona have posted an update on Microsoft's progress with the .NET Core tooling rebuild.


    MS is planning to introduce the first preview of this tooling in the next preview version of VS15. This paves the way for the new architecture of the .NET Core tooling to likely be released with the RTM of VS15.

    The current plan for NCrunch is to integrate with this platform as it becomes available with a goal to properly release this feature area alongside support for the next version of Visual Studio (VS 2017?).

  • Miro commented  ·   ·  Flag as inappropriate


    Could you please update on the estimated release of NCrunch with support for .NET Core projects?

    A stable version has been released and our teams would like to start using it. However this is currently blocked by not being able to use NCrunch with it.


← Previous 1 3

Feedback and Knowledge Base