Forum member
DCasado
30 posts
Posts by DCasado
-
Failing tests with XUnit v4 and DateTime parameters
Many thanks for the quick response. You are right, this is an issue with xunit itself. Upgrading to version v4.0.1. solved my problem.
16 Sep 2026 13:01 UTC
-
Failing tests with XUnit v4 and DateTime parameters
Hi, we updated to the latest version of XUnit (4.0.0) and NCrunch (5.23.0.1). Some of our tests are now failing and they all have a DateTime parameter: [code] using AwesomeAssertions; namespace NCrunchIssue { public class UnitTest1 { public static TheoryData<DateTim…
15 Sep 2026 12:42 UTC
-
xunit v3, missing xunit.v3.runner.inproc.console net6.0?
I can confirm that your fix is working on my side. Many thanks for the quick support!
08 Jul 2025 05:52 UTC
-
xunit v3, missing xunit.v3.runner.inproc.console net6.0?
I was able to reproduce this in a small repro: https://github.com/IT-CASADO/ncrunch-issue-01 The problem is related to the following project setting: [code=csharp] <UseArtifactsOutput>true</UseArtifactsOutput> [/code]
07 Jul 2025 08:59 UTC
-
xunit v3, missing xunit.v3.runner.inproc.console net6.0?
Just to mention: It also helps to include a direct package reference to my two projects.. [code=csharp] <ItemGroup> <PackageReference Include="xunit.v3.runner.inproc.console" /> </ItemGroup> [/code]
07 Jul 2025 08:08 UTC
-
xunit v3, missing xunit.v3.runner.inproc.console net6.0?
This is the error from the UI: [i]An error occurred while analysing this project after it was built: Unable to resolve an assembly required for the execution of Xunit3 on this machine. The assembly was expected at the following path: D:\.cache\nuget\xunit.v3.runner.inproc.console\2.0.3\lib\net6.…
07 Jul 2025 07:08 UTC
-
xunit v3, missing xunit.v3.runner.inproc.console net6.0?
Hi, today I run into the same problem. The only thing that currently is helping is: [quote=mgrundner;18047]As a workaround i currently do: <!-- TODO: Remove this after NCrunch solved: --> <PropertyGroup Label="https://forum.ncrunch.net/yaf_postst3559_xunit-v3--missing-xunit-v3-runner…
03 Jul 2025 21:32 UTC
-
NCrunch is building assemblies by just opening specific files in Visual Studio
I just installed the latest official version (v5.12) and now the issue is gone. Did you fix anything in the meanwhile?
25 Feb 2025 09:17 UTC
-
NCrunch is building assemblies by just opening specific files in Visual Studio
I'm able to reproduce this issue by - just creating a new .NET project in Visual Studio - adding a JSON file to the project - enabling NCrunch on the solution -- then every time you close the JSON file -- restarting the NCrunch engine -- opening the JSON file will trigger NCrunch to build the…
17 Feb 2025 10:50 UTC
-
NCrunch is building assemblies by just opening specific files in Visual Studio
I don't understand what's happing here :( I identified some other embedded files (*.json files) which have the same problem. I use KDiff3 to compare both files (from solution folder and from NCrunch workspace folder) in two different ways: [list=1][*]Opening the files directly by KDiff3 (in…
17 Feb 2025 10:30 UTC
-
NCrunch is building assemblies by just opening specific files in Visual Studio
I opened it from inside Visual Studio. Opening such files from external editors doesn't trigger NCrunch to build the assembly. It seems opening the same xlf file a second time doesn't trigger NCrunch to build. Comparing both files from disk with KDiff3 shows me that they are binary equal. But…
17 Feb 2025 08:15 UTC
-
NCrunch is building assemblies by just opening specific files in Visual Studio
Hi, I noticed that by just opening specific files NCrunch is building this assembly and all dependent. By just opening a file (configured as an embedded resource) SomeFile.[b]xlf[/b] Ncrunch is building the assembly and all dependencies. Is this normal behaviour? I just sen…
17 Feb 2025 07:31 UTC
-
Visual Studio Build Performance issues with NCrunch enabled
Build times for my complete solution: Without Visual Studio opened: 62 seconds With Visual Studio opened and NCrunch disabled: 62 seconds With Visual Studio opened and NCrunch ENABLED: 62 - 65 seconds :)
13 Feb 2025 13:46 UTC
-
Visual Studio Build Performance issues with NCrunch enabled
Just a note for other users who wants to switch to UseArtifactsOutput. I found one issue with EF Core (DOTNET EF command): [url=https://github.com/dotnet/efcore/issues/23853#issuecomment-2183607932]dotnet ef migrations fail when using custom output paths and separate project/startup-projects[/ur…
12 Feb 2025 14:09 UTC
-
Visual Studio Build Performance issues with NCrunch enabled
JFI: I changed other things (e.g. smaller NuGet packages) to reduce the build output size. New Build times for my complete solution with 5.12.0.7: Without Visual Studio opened: 53 seconds With Visual Studio opened and NCrunch disabled: 58 seconds With Visual Studio opened and NCrunch ENABLED: …
11 Feb 2025 08:48 UTC
-
Visual Studio Build Performance issues with NCrunch enabled
I can try this out.
11 Feb 2025 07:34 UTC
-
Visual Studio Build Performance issues with NCrunch enabled
Just to mention that I use also a Dev Drive.
10 Feb 2025 14:49 UTC
-
Visual Studio Build Performance issues with NCrunch enabled
If we don't have any other concerns with artifacts output than I would be fine this. I need to talk to other team members and give you an answer later. Many thanks so far for your support!
10 Feb 2025 10:26 UTC
-
Visual Studio Build Performance issues with NCrunch enabled
Just to mention that we also use Central Package Management. The artifacts output contains: - 25.514 Files -- 17.018 DLL files -- 4.082 PDB files - 4.088 Folders - size of 11 GB
10 Feb 2025 10:10 UTC
-
Visual Studio Build Performance issues with NCrunch enabled
is UseArtifactsOutput = true supported by NCrunch? I found this ([url=https://forum.ncrunch.net/yaf_postst3320_Support-for-central-Package-Management-and-Simplified-output-path.aspx]https://forum.ncrunch.net/yaf_postst3320_Support-for-central-Package-Management-and-Simplified-output-path.aspx[/ur…
10 Feb 2025 09:51 UTC