Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Metrics columns not showing

    Hi Mark, Thanks for posting. Something must have gone wrong with the settings for your columns in this window. The easiest option is probably to just wipe this part of the settings so that they can reset to default. Column sizes are stored in the *.ncrunchsolution.user file. If you look f…

  2. Xunit.v3 analysis failure

    I've implemented another fix for the Xunit DLL resolution issue in the build below, I'm hoping this solves the problem completely: [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_5.12.0.5.msi]NCrunch_Console_5.12.0.5.msi[/url] [url=https://s3.amazonaws.com/downloads.ncrunch.net…

  3. Xunit.v3 analysis failure

    I can't seem to reproduce the problem anymore after introducing the above fix. Are you able to reproduce it using a sample project that you can share with me? You can upload small projects to me in ZIP form through the [url=https://www.ncrunch.net/support/contact]NCrunch contact form[/url]. E…

  4. Xunit.v3 analysis failure

    Hi, Thanks for sharing this issue. I think I've managed to isolate it. It looks like the 'Copy reference assemblies to workspace' setting interferes with the Xunit3 assembly resolution. You can either disable this setting, or try the build below (in which I've implemented a fix): [url=https…

  5. Secondary monitor scaling issue

    ... Could you also confirm for me if adjusting the 'Optimize rendering for screens with different pixel densities' setting under your VS options (Environment->General) has any impact on this issue?

  6. Secondary monitor scaling issue

    Hi, thanks for sharing this issue. The tool tip window establishes the scaling factor from the monitor containing the control when it gets opened. Unfortunately, we've seen situations where some versions of Windows/.NET don't seem to report this correctly internally. I'm not sure if the issue…

  7. No supported projects detected after NCrunch update

    Thanks for sending through the bug report. It looks like the engine is discarding projects its loading, without any error present. Could we try resetting your configuration? While the IDE is closed, please delete the contents of C:\Users\USER\AppData\Roaming\NCrunch Once you've done this, …

  8. Aspire

    Thanks for sharing the ZIP. I've reproduced the problem as you've described it. I've spent some time trying to devise a way to get this to work. Unfortunately, I can't see a path to a solution .. not even a hacked up one. The root issue is that this particular toolset treats the entire solut…

  9. Aspire

    Try adding these missing files to the 'Additional files to include' project-level NCrunch configuration setting. I suspect they are somehow not being detected as dependencies, so they don't get copied into the workspace as they should be. It looks like these files are being created at load time wh…

  10. Aspire

    Thanks for sharing this issue. Can you check if the missing files are stored in the NCrunch workspace? I'm wondering if this could be as simple as just adding them to the 'Additional files to include' setting.

  11. Load runsettings

    [quote=hvkooten;17814]I'm the only one using NCrunch in the team (I don't know why), so I cannot change the code for this to work.[/quote] Sorry, we don't support runsettings. I can't suggest any workaround that does not involve changing the test code in some way.

  12. Load runsettings

    [quote=hvkooten;17812]As a contractor, at my current assignment, thay have integration tests setup next to unit tests. The environment settings are loaded as testcontext properties to switch between environments. I cannot change this process. Therefore I hope there is a way to inject and switch betw…

  13. Load runsettings

    Hi, thanks for posting. NCrunch's MSTest support is emulated rather than integrated, and the emulator does not support loading settings from .runsettings. Is there something you need from there?

  14. Issue using ReadOnlySpan construction

    I've conducted a more thorough investigation of this problem. It seems to be coming from unstable behaviour in the .NET runtime. The error itself seems to be intermittent, depending upon the contents of memory at the time. You can run several copies of the same test doing the same thing and all…

  15. You must install or Update .NET to run this application

    See here for a fix for this issue: [url=https://forum.ncrunch.net/yaf_postst3525_Unable-to-build-apps-with--older--Windows-SDK.aspx]https://forum.ncrunch.net/yaf_postst3525_Unable-to-build-apps-with--older--Windows-SDK.aspx[/url]

  16. Issue using ReadOnlySpan construction

    Thanks for sharing this issue and for the code sample. I've reproduced it as you've described. The problem is caused by an instrumentation clash between RDI and the inline span being created by the compiler. I've noted this down to see if I can find a way to properly resolve it. For the time bei…

  17. Xunit.v3 analysis failure

    NCrunch tries to load the Xunit assemblies relative to xunit.v3.core. This means that if you've referenced xunit.v3.core via assembly reference (and not through the Nuget package), it will try to find them in the wrong place. Can you show me how you're referencing xunit.v3.core? Note that if yo…

  18. Performance drop when upgrading from V4 to V5.9

    My suspicion here is that this problem is caused by tests with inconsistent execution times. If the time taken for tests to execute isn't consistent, NCrunch won't know how to optimise the processing queue correctly. This can result in the overall execution time to be widely inconsistent, with s…

  19. using dotnet secrets in tests fails

    Hi, thanks for sharing this issue. NCrunch itself is just a console application. It may be worth trying to build your own console application and loading the secrets from there, to see if there is a difference in how it works. NCrunch has no integration with dotnet secrets, and I confess that…

  20. Building with OpenApi generation

    Hi, thanks for sharing this issue. The root problem here probably comes from the package restore step, which is done by VS without the $(NCrunch) property active. This then causes the PackageReference to bleed into the project.assets.json file which is shared between between both VS and NCrunch.…