Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. .NET Core support for NCrunch (first public build)

    [quote=GreenMoose;9894] I've sent you the repro solution via email if you want to look into it in more detail.[/quote] Perfect, thanks! I'll get back to you on this soon.

  2. .NET Core support for NCrunch (first public build)

    v3.5 is now available with a fix for nunit.framework assembly resolution - [url=https://www.ncrunch.net/download]https://www.ncrunch.net/download[/url]

  3. .NET Core support for NCrunch (first public build)

    [quote=GreenMoose;9891]FWIW, if I create a new project in vs2017, copy the same source files, and then add the NLog dependency via nuget it builds fine. I plan to do this for all projects since I get a lot of miscellaneous warnings in vstudio regarding versions I don't want to spend time on :).[/quo…

  4. .NET Core support for NCrunch (first public build)

    [quote=GreenMoose;9888] I get a lot of test errors due to this is being invoked multiple times (as in a static member is already set). Moving it out to have "one time only" execution (guarded via static field) as part of normal setup in a test fixture resolves the issue. (I didn't get stacktrace e…

  5. .NET Core support for NCrunch (first public build)

    Before I put v3.5 up, I'd like to learn a bit more about the other bug report you just submitted. The project you have that NCrunch is failing to analyse is falling over because of a missing dependency, System.Diagnostics.TraceSource v4.0.0.0. Are you able to identify how this package is being…

  6. .NET Core support for NCrunch (first public build)

    Thanks, I just saw your bug report come through and I've reproduced the problem. NCrunch isn't resolving the nunit.framework assembly correctly when it uses newly initialised test processes that weren't used for discovery. You'll see this often if you are using NUnit under .NET Core and you have p…

  7. .NET Core support for NCrunch (first public build)

    v3.4 has now been released [url=http://blog.ncrunch.net/post/NET-Core-Support-Has-Arrived!.aspx]http://blog.ncrunch.net/post/NET-Core-Support-Has-Arrived!.aspx[/url].

  8. NCrunch is ignoring TestCaseSource cases where the test case ToString() is non-unique

    Just hit the 'show all warnings' button :) I've made a note to find better ways to inform of this problem and document it in better detail.

  9. .NET Core support for NCrunch (first public build)

    Hi, thanks for sharing this problem. Are these artifacts originating from a project your test project is referencing? If so, this isn't a problem specific to .NET Core - see [url=http://www.ncrunch.net/documentation/considerations-and-constraints_assembly-colocation-assumptions]http://www.ncrunch.…

  10. NCrunch is ignoring TestCaseSource cases where the test case ToString() is non-unique

    Hi Dylan, Thanks for sharing this problem. While I'm sure this feels like a bug when you hit it, it's actually a technical limitation with the design of the test framework itself. Both XUnit and NUnit share this problem and they exhibit it in different ways. NCrunch should give you a warni…

  11. Inconsistent compiler results

    Thanks for all your help and your patience :)

  12. Inconsistent compiler results

    Great work in narrowing this down. I've just set up a dummy project under VS2015, referencing the MS UnitTestFramework dll as it exists under VS2013, set it up over a grid, and bang .. it happened. I think this problem is related to the way NCrunch replicates this DLL over the grid. Probably it's…

  13. .NET Core support for NCrunch (first public build)

    [quote=shaynevanasperen;9869]Thank You! That solves the problem. I was missing System.Runtime.Serialization.Formatters and System.Diagnostics.TraceSource. After installing them in a dummy project I can now run my tests with NCrunch.[/quote] Excellent! Thanks for confirming this!

  14. .NET Core support for NCrunch (first public build)

    [quote=memark;9866]Doesn't the normal NCrunch trial period work for this build as well?[/quote] Yes and no. All NCrunch builds ship with the 30 day evaluation license, but once it's been used, you can't use it again, even in future versions. It's not ideal for test builds like this. To be ho…

  15. .NET Core support for NCrunch (first public build)

    [quote=shaynevanasperen;9865]I'm very disappointed. I just decided to purchase a licence so that I could try out this new build, only to discover after purchasing that it only lasts for one year. That should have been made clear before I purchased it. It wouldn't be so bad if the software actually w…

  16. .NET Core support for NCrunch (first public build)

    [quote=memark;9863]Oh ok, I see. No problem, I fully understand your reasoning. But it's still little confusing when you provide builds for all versions of Visual Studio in your post. You might consider removing the ones not actually supported, since users visiting this post probably came here to…

  17. .NET Core support for NCrunch (first public build)

    Sorry, I should have clarified. This build won't work with .NET core projects that are using xproj/project.json. It will only work with .NET Core projects as built from the VS project templates under VS2017. This is because the xproj/project.json system is built on a whole toolchain that has be…

  18. Inconsistent compiler results

    Ok, I think we're narrowing this down. My theory right now is that there is a specific code element causing this problem. The good news is that because this is your test project, it's likely at the top of the dependency structure, so it should be possible to deductively figure out which elemen…

  19. .NET Core support for NCrunch (first public build)

    I'm happy to announce the first public test build for .NET Core support in NCrunch. This build of NCrunch is able to load .NET Core projects, build them, instrument their assemblies, construct test environments and run xUnit/MSTest/NUnit tests end-to-end. Distributed processing has also been imple…

  20. Inconsistent compiler results

    I don't think this problem is likely to be caused by the MSBuild warnings. There must be a physical reason for the hash being different between these machines. Are both machines using x64 processors? Would you be able to walk me through the exact steps you've used to compare the two files using…