Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. VS on 100% CPU for several seconds on each build when NCrunch is disabled

    Hi, thanks for sharing this. There isn't really much of NCrunch that is active when it's disabled. However, it's definitely worth checking the logging situation. Can you check to see if NCrunch is set to 'Log to output window' in its configuration? If so, turn this off. Also make sure that …

  2. Licensing: need a new license for VS 2026?

    Hi, thanks for posting. The first version of NCrunch to support VS2026 is v5.18, though v5.18 doesn't work on .NET 10. If your current license maxes out at v5.8, then you'll need to upgrade the license to access the newer versions (of which I highly recommend the latest release, v5.20, which s…

  3. Rider freezes UI very often when combined with NCrunch

    Finally! I did have high hopes on that last fix. We were starving the thread pool for the IDE. It wasn't obvious, but the background threads being used for transferring NCrunch data into editor windows were being allocated from the same pool as the threads used by the IDE for everything else, w…

  4. Console Runner On A CI Server, Optimization Hints

    Great to hear that these settings changes have made a difference. The RDI data is probably just cached data being cycled between runs. If you clear out the .cache file being used by the console tool, in theory this should resolve the issue. LevelOfParallism is not an attribute used by NCrunch…

  5. The target "_SplitProjectReferencesByFileExistence" does not exist in the project.

    Hi, thanks for sharing this issue along with the sample project (it's so much easier with a code sample to help understand what's happening). For NCrunch to load a project, there is a critical property that must be present in the project, "TargetFrameworks". This is because we need to know the…

  6. Console Runner On A CI Server, Optimization Hints

    Hi, thanks for posting and for providing the configuration file. I'll try to answer your questions directly. 1. Disabling RDI for your console run is strongly recommended, as the console tool doesn't have a way to access/present RDI data in a useful way, so this tends to just result in I/O churn…

  7. Rendering each test case for an XUnit Theory

    [quote=ndeslandes;18471]Out of curiosity, how come this works as expected, producing one test report per theory use case? [/quote] This is because the types involved are primitives, so they are treated differently by xunit. User types are somewhat problematic because they are harder to reliab…

  8. Rendering each test case for an XUnit Theory

    Hi, thanks for posting. NCrunch doesn't support granular reporting of theories that use ClassData, because this requires the runner to deconstruct the xunit test metadata in detail (which is something we try very hard not to do, as it increases the fragility of the integration). If reporting t…

  9. Rider freezes UI very often when combined with NCrunch

    Thanks for sending through the log. Through an expensive process of deduction and rewriting a lot of code, there's probably not much left that can cause this. My latest suspicion is that the problem is being caused by thread pool starvation. I've implemented a change that I hope will solve it. …

  10. Rider freezes UI very often when combined with NCrunch

    [quote=TimVisma;18464]Unfortunately I still have the freeze problem.[/quote] Sorry, looks like I'm going to need another capture like the last one.

  11. nCrunch is very eager

    Hi Stian, Thanks for sharing this issue. Running on an engine mode set to 'Run all tests automatically' WILL aggressively queue up tests covering projects that have changed, but NCrunch normally shouldn't build projects that haven't changed. There are three notable exceptions to this: 1. If …

  12. Problem with latest xUnit v3 (3.2.0)

    v5.20 is now available, including a fix to implement support for xunit v3.2.

  13. xunit.v3 3.2.0 kills ncrunch build

    v5.20 is now available including the fix to implement support for xunit v3.2.

  14. Rider freezes UI very often when combined with NCrunch

    v5.20 is now available. I'm keen to hear it helps with the freezing issues.

  15. Rider freezes UI very often when combined with NCrunch

    Ok, I have more optimisations coming. Look out for them in the v5.20 release set to go out with Rider 2025.3, which I hope will be in the coming week.

  16. xunit.v3 3.2.0 kills ncrunch build

    A fix will be out for this in NCrunch v5.20, which I'm aiming to release with Rider 2025.3, which I'm hoping will be in the coming week.

  17. Problem with latest xUnit v3 (3.2.0)

    A fix will be out for this in NCrunch v5.20, which I'm aiming to release with Rider 2025.3, which I'm hoping will be in the coming week.

  18. xunit.v3 3.2.0 kills ncrunch build

    Hi, thanks for sharing this. This is a [url=https://forum.ncrunch.net/yaf_postst3633_Problem-with-latest-xUnit-v3--3-2-0.aspx]known problem[/url] at the moment. Xunit 3.2 has a breaking change for us. A fix will be coming in NCrunch v5.20. For now, I recommend staying on Xunit v3.1.

  19. New installation with VS2026

    Hi, thanks for sharing this. There seems to be things in the environment that can cause this problem, but I've never managed to pin them down. It could be something as simple as an aggressive virus scanner or firewall. The fix is usually simple though. Create a sample project that references…

  20. Rider freezes UI very often when combined with NCrunch

    Thanks for sending through the logs. It looks like there's more I can do here. I'll let you know as soon as I have another build available.