Forum member
nikize
9 posts
Posts by nikize
-
DirectoryNotFoundException: Could not find a part of the path 'D:\ncrunch\workspace\56184\132\...
No worries, I only expect this to work with the dotnet toolchain, and have reports internally that supports that as well. But yes we are mostly working around the problem. But if at least NCrunch works, there is a chance that others work as well? Was you able to make the DirectoryNotFoundExcepti…
29 Jun 2026 09:13 UTC
-
xUnit Collection handling
I both agree and disagree with the logic here at the same time. I understand there is no perfect solution, and I don't expect any fix, but I want to share a usecase. Let's assume this case [code] [Collection("FileGroupX")] [/code] Regardless if my tests run in NCrunch or any other test run…
14 Jun 2026 03:19 UTC
-
DirectoryNotFoundException: Could not find a part of the path 'D:\ncrunch\workspace\56184\132\...
This is on vs2026 Since we in the first case see nCrunch.Common.IO.FilePath in the stack, I assume that it is the ncrunch process that hits this, maybe there is other cases as well, but the first case shouldn't happen if long path support was working in the ncrunch process.
04 Jun 2026 00:46 UTC
-
DirectoryNotFoundException: Could not find a part of the path 'D:\ncrunch\workspace\56184\132\...
Thanks for the extensive explanation. Yes I could probably handle the remaining case with a even shorter path, while unfortunately current project does not really allow for me to move things around or rename. My thinking of the documentation page is to under the "to long path" header have someth…
03 Jun 2026 12:57 UTC
-
DirectoryNotFoundException: Could not find a part of the path 'D:\ncrunch\workspace\56184\132\...
Just got similar: [code] The file 'C:\dev\projpath\obj\Debug\netstandard2.0\projname.GlobalUsings.g.cs' could not be written to the workspace due to error: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\MyUser\AppData\Local\NCrunch\46876\35\projpartialpath\obj\…
03 Jun 2026 11:02 UTC
-
No Exception output with NUnit 4.4.0 NCrunch 5.16.0.5
Interesting, would it be worth trying to get some kind of detection into NUnit so that if NCrunch < 5.17 is used it reverts to the old way of reporting? (on the other hand, we can force NUnit 4.3.2) It has maybe been a week of head scratching as to why I didn't get any explanation on test failure…
28 Aug 2025 13:19 UTC
-
No Exception output with NUnit 4.4.0 NCrunch 5.16.0.5
Having Issues with NCrunch not showing the stack for exceptions in Trace Output After some theories, my tests shows that NUnit 4.3.2 works (shows stack output), but 4.4.0 does not. Is this just me? .csproj: [code=xml]<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFrameworks…
28 Aug 2025 09:45 UTC
-
UserException from AnalyseComponentBuild with VS 17.4 Solved with NC v5.14
Thanks, Confirming that it does work with v5.14 License upgrade purchased (this is my personal account, the license actually used is on a different, company owned account)
15 May 2025 08:09 UTC
-
UserException from AnalyseComponentBuild with VS 17.4 Solved with NC v5.14
With upgrade to Visual Studio Version 17.14.0 yesterday these issues have been seen on multiple machines in different solutions NCrunch 5.13.0.4 and earlier (My license was valid to 2025-04-24), so have not been able to test 5.14 Rollback to VS 17.13.6 and NCrunch is working again dotnet --list…
15 May 2025 06:52 UTC