Forum member

Fasopus

6 posts

Posts by Fasopus

  1. .NET 4.7.1 Support

    The specific feature we were targeting in 4.7.1 was the improved Net Standard 2.0 support, allowing a large number of binding redirects to be removed and trimming down the size of our build output.

  2. .NET 4.7.1 Support

    Is there any timeline for .NET 4.7.1 support being added to NCrunch? I realize that it has only be released for a week but our team has been diligently keeping our .NET versions up to date.

  3. NCrunch not showing coverage with NUnit TestCaseSource VS2017

    Cleared my caches, installed the update, and everything looks like its working properly now! Thanks for the update!

  4. NCrunch not showing coverage with NUnit TestCaseSource VS2017

    [quote=Remco;10587] I've managed to make some progress today towards a proper fix. It's complex, but I'm optimistic. I'll let you know when I have something available. [/quote] Don't want to rush you, but is there any update on this? We've tried working with the suggested workaround but we ar…

  5. NCrunch not showing coverage with NUnit TestCaseSource VS2017

    Thank you for looking into this and suggesting a workaround. I believe this issue could also be solved by switching the .NET framework test project to be a netstandard test project? The reason we are using a .NET framework is because one of the tools we use for arranging our tests (Autofixture) …

  6. NCrunch not showing coverage with NUnit TestCaseSource VS2017

    After switching to VS2017 and transitioning several of our full framework test projects to utilize the new project file format, our team has noticed that NCrunch is no longer displaying code coverage for several classes that are tested by NUnit TestCaseSources. It should also be noted that in these …