Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Cannot get Rx.NET to work with NCrunch

    [quote=onovotny;10026]I really don't like the idea of putting tool specific information in my project file like that. It would be much cleaner if NCrunch could read the TFM list and then use a /p:TargetFrameworks=foo parameter as it builds and can filter out only the TFM's it supports (net and netco…

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

    [quote=Grendil;10030] Hi, thanks for following up with me. The project where I encountered the bug is a large solution with many interdependencies. I created a new project and tried to reproduce the bug there but so far I haven't been able to. I must be leaving out a critical element in my simpli…

  3. NCrunch, Core 1.0.1 and BadImageFormatException

    [quote=Rasmus;10029] I cant get my sample project to have any of these issues and I cannot share the original.[/quote] Sorry, I wish I could be of more help, but I won't be able to help troubleshoot this without a sample :(

  4. NCrunch fails to start debugging tests

    [quote=offset123;10028] Is it possible to downgrade NCrunch from v3.6 to v3.3 without losing the existing configurations? I don't really need VS2017 and Core stuff. [/quote] Yes, I believe so. I haven't personally tested this, but in theory v3.3 should be forwards compatible with v3.6 configur…

  5. build failed on Resharper Change Signature function

    Ok, this is a limitation of the impact detection then. When you use this engine mode, NCrunch will only queue tests for execution when the impact detection flags them as being impacted by a change. Because the impact detection is not 100%, there are known situations where changes to code will no…

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

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

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

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

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

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

  12. NCrunch, Core 1.0.1 and BadImageFormatException

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

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

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

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

  16. 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. 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?

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

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

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