Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Different NCrunch file naming for slnx

    Can you confirm 100% whether downgrading to 5.15.0.3 resolves the issue? The fix for this problem was rolled into the 5.15.0.4 build on the download page. If you're experiencing this problem with the latest build, my suspicion is that there may be an element here that hasn't been fully fixed, or a …

  2. NUnit 4 and ParallelizableAttribute

    Hi, thanks for posting. [quote] Questions: 1) Does this mean that NCrunch can more reliably and automatically disable parallel test runs with xUnit, but not with NUnit? [/quote] Yes. Xunit has a configuration option that, when passed in, can shut off all parallel behaviour. Our control ov…

  3. Help debugging issue with impacted tests detection

    Ok, the problem is called by the CallerFilePathAttribute declared on Xunit's FactAttribute constructor. This causes any code instantiating a Fact to have its source file path encoded as a const inside the assembly. Because the file paths change depending on which NCrunch workspace is building th…

  4. Help debugging issue with impacted tests detection

    Great work narrowing this down. I've reproduced it as you've described - switching the Xunit dependency seems to surface the problem. I'm taking a closer look and will let you know when I have more info.

  5. Help debugging issue with impacted tests detection

    Thanks for these extra details, and for submitting the bug report. On the Tests Window, could you right-click the column headers, then turn on the 'Is Impacted' column? This will let us check whether the problem is in the impact detection, or whether it's related to how the tests are being queue…

  6. Help debugging issue with impacted tests detection

    Hi, thanks for posting. Could you confirm which engine mode you are currently using? Also, could you submit an NCrunch bug report immediately after this happens?

  7. Rider: Elapsing Ignored Test in NCrunch Test Windows on unignoring

    Thanks. I'll check it out.

  8. Rider: Elapsing Ignored Test in NCrunch Test Windows on unignoring

    It's possible you have an ignored test selector that is causing some hierarchical problems. Check your settings files for the ignore selectors and try removing them manually (with the IDE closed). Ignoring and unignoring at project level should normally work.

  9. Rider: Elapsing Ignored Test in NCrunch Test Windows on unignoring

    Hi, thanks for sharing this issue. The Tests Window doesn't work very well for the ignore/unignore options when set to organise tests by category. The reason for this is because of the way ignored tests work internally in the engine. When you ignore a test, the engine creates and stores a con…

  10. Unable to exclude .txt files from triggering tests to run

    Hi, thanks for posting. The 'Run all tests automatically' engine mode is fairly indiscriminate. It will run every test in a project that passes through the build system. Because there's no reliable way to know which files contribute to the build, any changed file in a project will trigger a bui…

  11. xunit v3, missing xunit.v3.runner.inproc.console net6.0?

    Here's a fixed build for you. [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_5.16.0.3.msi]NCrunch_Console_5.16.0.3.msi[/url] [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_5.16.0.3.zip]NCrunch_Console_5.16.0.3.zip[/url] [url=https://s3.amazonaws.com/dow…

  12. xunit v3, missing xunit.v3.runner.inproc.console net6.0?

    Thanks for narrowing this down. It looks like this problem is caused by xunit switching to net8, so the path has changed. I'll see about implementing a fix.

  13. xunit v3, missing xunit.v3.runner.inproc.console net6.0?

    As far as I'm aware, any widespread issues of this sort have been resolved in the later builds of NCrunch. With that said, it's quite possible that certain build configurations can still give dependency errors around Xunit3. Can you share more detail around the project you're experiencing proble…

  14. Rider: Any NCrunch ToolWindows in Windows Mode steals Focus

    [quote=Der-Albert.com;18213] I could reproduce it when NCrunch had detected build errors for a project, and I clicked in the NCrunch Tool Window on the Line with the Error, and was unable to type anything in that opened Document, But I could type in other already open document windows [/quote]…

  15. Rider: Any NCrunch ToolWindows in Windows Mode steals Focus

    Thanks for sharing this. Are you able to provide step by step instructions on how to get the editor into a state where it does not accept any input?

  16. Rider prompts to install .net runtime 6.0.36 after every reboot

    [quote=aledmorris2;18207] I've installed the SDK rather than the runtime but I'm expecting a visit from the software police in the near future who will tell me it's not allowed (out of support) [/quote] In theory, the runtime should be enough. I'll admit that I never tested it with just the ru…

  17. Rider prompts to install .net runtime 6.0.36 after every reboot

    NCrunch requires .NET 6 to be installed when working under Rider. I'm not sure how reliable the message prompts for installing this are, but downloading the SDK and installing it manually should definitely solve this. [quote=aledmorris2;18205] Just now (5 hours after that) the NCrunch process w…

  18. Rider prompts to install .net runtime 6.0.36 after every reboot

    Can you check the contents of your Program Files\dotnet\sdk directory and list for me the versions of .NET that you have installed?

  19. Rider prompts to install .net runtime 6.0.36 after every reboot

    Hi Aled, Thanks for sharing this issue. Can you confirm precisely when you receive the prompt to install .NET? Is this when the NCrunch engine starts? Or when you open a solution in Rider? Or perhaps when you run a test?

  20. Unable to build net9.0 isolated Azure Functions

    [quote=emsurgecto;18197] This worked for me, thank you! Does it have any negative implications? [/quote] So far I know of none. However, it's impossible to account for every toolset. If you don't see any problems with the build completing, then it's a safe bet that you're OK.