Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Build failure in VS2017

    Sorry, I wish I had an easy way to figure out what was happening here :( Somewhere there must be logic telling the build system where to find these files. Please do let me know if you manage to isolate this problem.

    09 Mar 2017 10:09 UTC

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

    Ok, I've figured out the System.Diagnostics.TraceSource resolution issue. This is happening because the unit test project is set to target netstandard, rather than netcoreapp. When projects are built for netstandard, they are platform-independent and do not have the .deps bindings for platform…

    09 Mar 2017 00:45 UTC

  3. 3.5.1 installer installs only in one VS 2017 Instance

    Hi Albert, This is correct. I've yet to find a way to produce an MSI that can target multiple install locations dynamically. I had expected multiple installations of VS2017 to be quite a rare edge case :) It is still possible to install to multiple IDEs, but you'll need to do a manual instal…

    08 Mar 2017 23:19 UTC

  4. Build failure in VS2017

    Hi, thanks for sharing this problem. VS2017 introduced a complex change to MSBuild dependency resolution under which the references are no longer stored in the GAC. This means they can only be loaded from known locations. The IDE works around this problem through a series of binding redirection…

    08 Mar 2017 23:17 UTC

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

    For NCrunch.Framework, you'll need to use the NCrunch.Framework.DotNetCore.dll that's sitting in the NCrunch installation directory (under VS extensions/RemcoSoftware). This will be published through the NCrunch NuGet package when I find a clean way to do this :)

    08 Mar 2017 23:06 UTC

  6. .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.

    08 Mar 2017 11:53 UTC

  7. .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]

    08 Mar 2017 11:11 UTC

  8. .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…

    08 Mar 2017 11:01 UTC

  9. .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…

    08 Mar 2017 10:43 UTC

  10. .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…

    08 Mar 2017 10:23 UTC

  11. .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…

    08 Mar 2017 10:03 UTC

  12. .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].

    08 Mar 2017 00:37 UTC

  13. 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.

    07 Mar 2017 22:16 UTC

  14. .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.…

    07 Mar 2017 22:15 UTC

  15. 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…

    03 Mar 2017 22:46 UTC

  16. Inconsistent compiler results

    Thanks for all your help and your patience :)

    02 Mar 2017 06:38 UTC

  17. 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…

    01 Mar 2017 22:22 UTC

  18. .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!

    01 Mar 2017 22:09 UTC

  19. .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…

    01 Mar 2017 12:05 UTC

  20. .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…

    01 Mar 2017 12:00 UTC