Forum member

spolonski

53 posts

Posts by spolonski

  1. NUnit failed to discover the tests in this assembly

    The Setting Preload assembly references didn’t change the exception behavior. I did migrate the project from NUnit to xUnit (AI did this automatically), and that’s when I noticed that another assembly couldn’t be loaded because it wasn’t signed. Thanks for helping me investigate the issue.

    24 Feb 2026 06:54 UTC

  2. NUnit failed to discover the tests in this assembly

    [quote]So it was triggered by a config change that was introduced to work around a different issue. [/quote] Yes. [quote]There is something unusual in the way your assembly references are working. I haven't seen instrumentation cause this kind of problem before, since it doesn't tamper with the…

    23 Feb 2026 10:54 UTC

  3. NUnit failed to discover the tests in this assembly

    I tracked it down to the commit causing the issue. It was a change to the NCrunch settings in another assembly. That assembly is no longer supposed to be instrumented. I changed in UI InstrumentOutputAssembly = false. Unsure about PreventSigningOfAssembly. [code=diff] diff --git a/Application/Sou…

    20 Feb 2026 12:11 UTC

  4. NUnit failed to discover the tests in this assembly

    I can reproduce failures and passes at different code stages, but I have to restart the NCrunch engine to see the difference.

    20 Feb 2026 08:33 UTC

  5. NUnit failed to discover the tests in this assembly

    [quote=Remco;18654]Thanks for sending through the log. Does starting the test with a debugger attached and wide settings on exception filters cause the exception to be trapped? [/quote] If I right‑click an assembly in the NCrunch Test Window and choose Debug, the debugger does not attach at all. …

    20 Feb 2026 07:19 UTC

  6. NUnit failed to discover the tests in this assembly

    [quote=Remco;18651]Are you able to make any guesses as to what change might have caused this? Did you upgrade your NUnit dependency? Is there any chance you could submit a bug report right after the failure?[/quote] I have no idea (maybe dot net sdk 10, but not on Grid Server), as far as i can sa…

    20 Feb 2026 04:53 UTC

  7. NUnit failed to discover the tests in this assembly

    NCrunch Version on BuildServer: 5.15.0.4 Local: 5.20.0.2

    19 Feb 2026 13:33 UTC

  8. NUnit failed to discover the tests in this assembly

    <PackageReference Include="NUnit"> <Version>4.4.0</Version> </PackageReference> <PackageReference Include="NUnit3TestAdapter"> <Version>5.2.0</Version> </PackageReference>

    19 Feb 2026 13:30 UTC

  9. NUnit failed to discover the tests in this assembly

    I don’t know why, but the tests in one assembly suddenly stopped working. An error occurred while analysing this project after it was built: NUnit failed to discover the tests in this assembly: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more info…

    19 Feb 2026 13:27 UTC

  10. Distributed Processing in Rider is empty

    Yes, that helped. Why can the VS plugin handle it on its own?

    24 Mar 2025 14:33 UTC

  11. Distributed Processing in Rider is empty

    Done

    24 Mar 2025 06:47 UTC

  12. Distributed Processing in Rider is empty

    When I try to add an existing in VS Node, then i can see an Error Message "This server has already been added to the list of known servers". When I try to add an new Node, then it doesn't appear in the list. But it appear in global config file.

    21 Mar 2025 09:42 UTC

  13. Distributed Processing in Rider is empty

    Hi Remco, The window is rendered correctly. Only the nodes are missing. Regards, Sergei

    21 Mar 2025 06:33 UTC

  14. Distributed Processing in Rider is empty

    Hi Remco, In Rider, the Distributed Processing window is empty, whereas in Visual Studio on the same machine, there are three nodes Both NCrunch Versions are 5.12.0.10 Regards, Sergei

    20 Mar 2025 13:50 UTC

  15. Portable vs Full pdbs

    Thanks, Remco. It works like a charm!

    22 Jan 2025 08:36 UTC

  16. Portable vs Full pdbs

    Hi Remco, we are not using anything like that. Yes, I am interested in the fix indeed. Thank you in advance.

    21 Jan 2025 11:19 UTC

  17. Portable vs Full pdbs

    Hi Remco, Yesterday, NCrunch threw an error: "System.ArgumentOutOfRangeException: Arrays larger than 2GB are not supported" in one of the projects. After that, we changed the DebugType to "portable" in all projects. The test ran successfully from the IDE. However, today, several projects launch…

    21 Jan 2025 06:29 UTC

  18. NullReferenceException at nCrunch.Common.IO.DiskPath.DoRebase

    Just what the doctor ordered.

    15 Jan 2025 11:33 UTC

  19. NullReferenceException at nCrunch.Common.IO.DiskPath.DoRebase

    Thanks Remco, That helps me. The variable OutDir is currently set in Directory.Build.props without a condition. I will play with a condition property. <Project> <PropertyGroup> <OutDir>c:\Program Files (x86)\Common Files...</OutDir> </PropertyGroup> </Project>

    15 Jan 2025 11:26 UTC

  20. NullReferenceException at nCrunch.Common.IO.DiskPath.DoRebase

    Hi Remco, I submitted the bug report with a title "NullReferenceException at nCrunch.Common.IO.DiskPath.DoRebase". I have not included any files myself in configuration for this solution.

    15 Jan 2025 10:42 UTC