Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. ASP.NET Core Build

    Can you try adding the following line of code into the primary PropertyGroup in your project file? <TypeScriptCompileBlocked Condition="'$(NCrunch)' == '1'">true</TypeScriptCompileBlocked>

  2. ASP.NET Core Build

    Hi Michael, Thanks for sharing this issue. Deactivating TypeScript compilation under NCrunch is often worthwhile as it can improve performance and suppress issues like this. This in particular looks like a dependency issue on the grid node. Can you confirm if you're able to build this partic…

  3. Custom nuget.config causing Nuget restore warning

    [quote=VNicholson;13777] Are there plans to make NCrunch respect the nuget.config overrides so it installs dependencies to the specified globalPackagesFolder? Presumably that would also get rid of the spurious warning?[/quote] Yes, and yes :)

  4. Custom nuget.config causing Nuget restore warning

    Hi, thanks for sharing this issue. In your case, this error is probably more of a warning. It's being caused by an internal discrepancy between your redirected package path and the default global packages directory on your system. Essentially, NCrunch has tried to install several packages it su…

  5. NCrunch support for tests in .razor files

    In theory, NCrunch should support any source file that has debugging information present in the output PDB file. In practice, we've never tested this with razor files. I honestly didn't know it was possible to build such a structure. Could I convince you to provide us with a small sample proj…

  6. "Deterministic builds only support portable PDBs" in F# project

    Looking at how this is working, I expect that everyone using FSharp with NCrunch will likely need to adjust their .fsproj file for it to work correctly after updating their VS. Interestingly, when I tried the <Deterministic> flag inside the project file, it didn't work for me. Hence the suggesti…

  7. Receiving test errors after updating to 3.29

    [quote=DanAtkinson;13761][quote=Remco;13759] I'm not sure what the next steps are for this. This appears to be a solution (thank you!) but I'm not sure if it's intended to be a permanent one, or what the impact of it will be. [/quote] Excellent. I can now guess with reasonable accuracy what is…

  8. Nullable Type is not supported

    This could be a referencing error of some kind in disguise. Are you able to reproduce this in a sample project you can share with me? You can submit small code samples through the [url=https://www.ncrunch.net/support/contact]NCrunch contact form[/url].

  9. Receiving test errors after updating to 3.29

    Could you try deactivating the following two config settings at solution level (or for all projects in the solution) and confirm for me if this makes any difference in the error? [url=https://www.ncrunch.net/documentation/reference_project-configuration_instrument-output-assembly]Instrument outpu…

  10. Receiving test errors after updating to 3.29

    Thanks for these extra details. Could you try running one of the tests that consistently produces this problem with the VS debugger attached? (i.e. use the debug option in NCrunch). Make sure you have your exception settings to break on ALL exceptions. At the moment I'm strongly suspecting th…

  11. NCrunch could deliver a little more detail with exceptions on analysis

    Thanks for sharing this. It does look to be an internal exception kicked up by Xunit. The stack trace above doesn't seem to be complete. I'm not sure if this is due to the availability of debug information, but there is at least one step missing on the call stack here. When we discover tests, …

  12. Receiving test errors after updating to 3.29

    Thanks for sharing this issue. The error message describes a situation where the test execution process suddenly disappears without warning. This makes it hard to establish the source of the problem as the process likely took any error information with it. I hope you'll excuse the questions bel…

  13. serious typing lag when running NCrunch in VS2019

    Thanks for taking the time to go into so much detail on this issue. With the information you've provided, my best empirical analysis is that the issue is caused by overall resource load on your machine interfering with the responsiveness of the IDE. NCrunch makes use of a O/S level feature calle…

  14. Nullable Type is not supported

    Hi, thanks for posting. This message is a bit misleading in that although NCrunch is reporting it, the message is actually coming from the compiler and we have very little to do with it. Are you experiencing a difference in the compiler results between NCrunch and VS?

  15. "Deterministic builds only support portable PDBs" in F# project

    Can you try adding the following into the primary property group in your .fsproj file? <OtherFlags>--deterministic-</OtherFlags>

  16. ERROR (Build): TEST_svcHMRMgr_Library: (0): System.NotImplementedException: GenericInst

    Hi, thanks for sharing this issue. This problem is being triggered by an unexpected IL signature in the parameter of the attribute constructor call. Probably, it's specific to VB, which is why it's survived for so long and we haven't seen it before. We're reworking all this code at the moment…

  17. VS Crash - A heap has been corrupted

    [quote=Silvenga;13735] What kind of sucks is that I can't live without NCrunch or R# :D - my productivity will definitely drop to test if either one causes the problem. If you don't think NCrunch is at fault, then I'll likely have to live with it. R# and VS is unlikely to provide any help with NCru…

  18. serious typing lag when running NCrunch in VS2019

    [quote=NeilMacMullen;13736]I was just about to post about this bug but saw this thread. The 3.30.0.1 build definitely seems to help massively in getting back to the original performance but I think I can still detect a little lag - particularly noticeable as a slight delay when waiting for the Inte…

  19. Additional files to include not copying all files

    Hi, thanks for sharing this issue. The notation '**' inside a directory name isn't a supported structure of NCrunch's wildcard resolver. So the path '..\packages\MyDir\runtimes\**.*' is valid, but '..\packages\**\runtimes\**.*' is not supported. The code makes no special allowance for a '**' …

  20. Are Runtime Identifiers supported?

    If I understand this, the main issue is that by default, NCrunch doesn't place these files adjacent to the referencing assembly inside the build output directory. There are many toolsets and setups that require files to be collocated. In many cases we've adopted workarounds to force them into co…