Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. NCrunch fails to start debugging tests

    [quote=offset123;10021] Do you have any estimates on when the next version will be released? Right now using NCrunch is a pain (and the problem with file changes not being detected is still occurring).[/quote] Sorry, I can't make any promises on this right now. Things have honestly gone complet…

    19 Mar 2017 12:06 UTC

  2. build failed on Resharper Change Signature function

    [quote=offset123;10022] A very similar behavior (not necessarily caused by R# refactoring) is still occurring. I have a bunch of tests that seem to be running on an older version of the SUT and they report failing errors even though the code is OK. If I run the same test with R#, they are passing. …

    19 Mar 2017 12:04 UTC

  3. Cannot get Rx.NET to work with NCrunch

    From v3.6, NCrunch supports multi-targeted projects by splitting them out into virtual projects within the engine. This naturally means that each target will be built independently. Forcing the engine to work with a single target would greatly restrict the application of the engine (essentially re…

    19 Mar 2017 07:44 UTC

  4. Support for xUnit 2.2

    Hi Oren, The binding redirections were needed because the xunit components have been split between libraries, for example, there is xunit.core.dll which is the assembly used for attribute declarations, then there are xunit.abstractions.dll and xunit.execution.desktop.dll for the runtime execution…

    19 Mar 2017 07:37 UTC

  5. Cannot get Rx.NET to work with NCrunch

    Hi, Sorry but universal windows applications are not currently supported by NCrunch. Are the problems you are encountering related only to UWP projects?

    18 Mar 2017 22:47 UTC

  6. Support for xUnit 2.2

    Hi, yes this is on the list of things to address. Note that if you are using NCrunch with .NET Core, it will always use the version of xunit you are referencing from your test project.

    18 Mar 2017 22:44 UTC

  7. NCrunch, Core 1.0.1 and BadImageFormatException

    Is there any chance you could share a sample project with me?

    18 Mar 2017 22:43 UTC

  8. Debugging Async Tests - variable "does not exist in the current context"

    Hi, this could be a problem with the debug metadata. Are you able to reproduce this in a code sample you can share with me?

    18 Mar 2017 05:31 UTC

  9. Tests not discovered in net462 CPS .csproj

    Hi, Thanks for sharing this problem. I've reproduced it exactly as you've described. The problem is caused by NCrunch's IL hashing for impact detection. The recursion here is causing the IL hashing algorithm to bomb out with a stack overflow. I'll see what I can do to implement a fix. …

    17 Mar 2017 22:59 UTC

  10. Build fails due to dependency on .git directory

    Hi, Thanks for sharing this problem. This probably happens because NCrunch makes a copy of the project into its own workspace when it executes a build. This copy doesn't have the .git directory available, so the build target fails. There are two ways to solve this problem: 1. Include the …

    17 Mar 2017 22:51 UTC

  11. NCrunch fails to start debugging tests

    Thanks for sharing this problem. Although it doesn't appear the same way for me, I've seen some similar issues around this component lately. I have some ideas on things I can try. I'll try to get a speculative fix included for this in the next release.

    17 Mar 2017 22:46 UTC

  12. NCrunch, Core 1.0.1 and BadImageFormatException

    I just had an idea. Could you check whether your test project has a direct dependency on the two packages reported by the exceptions? If not, does adding the dependency directly resolve the problem?

    17 Mar 2017 22:27 UTC

  13. NCrunch, Core 1.0.1 and BadImageFormatException

    Ok, we're now stepping outside the boundary within which I feel I can be of much help here. Under .NET Core, it's the responsibility of the host process to declare the dependencies it requires and to load them in a way that complies with the 'rules' (which are to my knowledge completely undocumente…

    17 Mar 2017 12:33 UTC

  14. NCrunch, Core 1.0.1 and BadImageFormatException

    [quote=Rasmus;9989] The System.Runtime.InteropServices.RuntimeInformation ones are all in the self-hosted tests that uses TestHost/Kestrel. And all of those tests fail. The System.Net.Http.dll ones are more or less w/o rhyme or reason. These are mocked tests (moq) and hence quite self-contained. […

    17 Mar 2017 12:08 UTC

  15. NCrunch, Core 1.0.1 and BadImageFormatException

    Hi Rasmus, Sorry, let me confirm the exact name of the file. It should normally be nCrunch.TaskRunner.DotNetCore.x64.deps.json. This file will exist in the build output directory of the workspace used to execute your tests. You should be able to find it by right-clicking on the test in the Tes…

    17 Mar 2017 11:32 UTC

  16. NCrunch, Core 1.0.1 and BadImageFormatException

    Hi Rasmus, Thanks for sharing this problem. This exception is thrown by the .NET Core CLR when an attempt is made to load an assembly reference directly from the Nuget packages directory. Reference assemblies should normally be loaded automatically by the CLR using the NCrunch.TaskRunner.DotN…

    17 Mar 2017 09:47 UTC

  17. Any Plans to optimize ASP.NET, .NET Core Experience?

    Hi Albert, If you haven't already, I recommend giving the new version (v3.6) a spin. This included several changes to improve performance around synchronisation of .NET Core codebases. That aside, can you share any more details about performance issues your experiencing? Which actions seem u…

    16 Mar 2017 23:12 UTC

  18. Error occurred while analysing project

    [quote=Lawrence;9982]I'm seeing this same error now on my build box and I'm running 3.6.0.2 of the console app. However I'm using xUnit and VS2105[/quote] Hi, thanks for sharing this problem. The exception message given at the top of this thread is a very broad message given for when NCrunch h…

    16 Mar 2017 23:11 UTC

  19. NCrunch Runs Wrong Test(s)

    Hi Ed, Internally, NUnit uses sequentially generated IDs to represent the tests it discovers. NCrunch can't use these IDs between different versions of your assembly/project, because it's natural that the list of tests in the project could be changed while you work. You add them, remove them,…

    16 Mar 2017 23:04 UTC

  20. VS2017 Custom.After.Microsoft.Common.targets was not found

    [quote=osoykan;9976] Great! it works. But i was wondering, is this problem related with my configuration or ncrunch. Because there is no v15.0 folder, i created it. Actually there is "15.0" folder, so Did we change the VS 2017's behaviour?[/quote] For some reason, there is a property in your bui…

    16 Mar 2017 11:13 UTC