Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. One project (suddenly) builds very slow on NCrunch grid servers

    Hi, thanks for sharing this issue. 10 minutes is well on the extreme side for even the largest of projects. This definitely does not sound like normal behaviour. The structure of the build system as used by NCrunch is extremely variable and it depends on the version of VS/MSBuild being used. …

  2. Console tool, -GridServerReferencesForSolution results in InvalidCastException

    This configuration is a bit of an odd one in that we actually have two instances of it: GridServerReferencesForSolution GridServerReferencesForComputer When creating the list of all servers that should be connected to, the NCrunch client will take values from both of these settings. This mea…

  3. T4 Template generation fails in 3.18

    Thanks! We'll take a look and will get back to you.

  4. False trojan alert for nCrunch.TaskRunner.DotNetCore.20.x86.dll with Avira

    Thanks for flagging this up with Avira. We seem to get these sorts of things more and more these days. When malware gets more aggressive, so do all the scanners.

  5. System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

    Thanks for these extra details. The most likely source of these problems is the obfuscated reference assemblies. Obfuscated assemblies don't adhere to normal conventions (sometimes they actually fail a PEVerify check). This is deliberate as obfuscators are designed to prevent exactly what NCrun…

  6. why "unable to run concurrently" warning?

    Hi, thanks for posting. This warning gets triggered automatically by the engine when either the [url=https://www.ncrunch.net/documentation/reference_global-configuration_max-number-of-processing-threads]Max Number Of Processing Threads[/url] is set to 1, or [url=https://www.ncrunch.net/documentat…

  7. System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

    Hi, thanks for posting! There's a couple of possibilities here. The first is that it could well be the structure of your assembly is such that it's making NCrunch's IL analysis system particularly hungry. This could happen if, for example, you have a very large number of deeply nested methods. …

  8. Wrong assembly version copied to _ncrunchreferences

    Hi Malte, Thanks for sharing this issue. With VS15.8, MS introduced an assembly referencing redirection hack that affected some versions of .NET. This has caused a chain of issues for us, as it means that projects now need to be built with one version of assembly while referencing a different…

  9. Tests don't run on the grid from TC after upgrade

    There's something very suspicious happening here. We've just in the last 24 hours experienced the exact same issue in our own environment, shortly after installing the latest version of .NET Core on our grid nodes. It only affected our .NET Core test projects. And just like that, it suddenly …

  10. Tests don't run on the grid from TC after upgrade

    Hi, thanks for sharing this issue. The console tool has seen major development since the v3.9 release. The UX has changed completely and the handling of many of the conditions inside the run has also changed to better reflect the needs of CI systems. The first thing I would do is increase you…

  11. NCrunch errors after update to latest version 3.20

    Thanks for the extra details. We're aware of this problem but are struggling to find a way to reproduce it. [url=https://forum.ncrunch.net/yaf_postst2557p2_T4-Template-generation-fails-in-3-18.aspx]See here[/url] for a related report from another user. If you're able to share a sample project t…

  12. NCrunch errors after update to latest version 3.20

    Hi, thanks for posting! In v3.19/v3.20, we had to urgently address some assembly referencing issues that were introduced by the VS 15.8 update. It's possible that in doing this, we've broken something at your end. Can you check whether turning on the 'Copy referenced assemblies to workspace' …

  13. Testing Projects with Code Analysis enabled fail on Grid Node Server with Version 3.19.

    This custom property only gets applied when NCrunch builds your project, so there's no risk of side effects here. The property is the same one that NCrunch is actually supposed to inject into your build anyway (since CodeAnalysis is off), but somehow this is misbehaving. We'll get to the bottom of…

  14. T4 Template generation fails in 3.18

    [quote=smitchamb;12641]Touching back in on this thread. I've made some updates for VS 15.8 in the original text templating code and it doesn't appear to be an issue any more. However, I haven't been able to cut back the project to reproduce the runtime error in a minimal fashion. I'm hoping to get…

  15. Testing Projects with Code Analysis enabled fail on Grid Node Server with Version 3.19.

    Hi, thanks for sharing this issue. Another user has also reported this problem. v3.19 contained some refactoring around the code analysis suppression that shouldn't have resulted in a functional change, but apparently in some environments it has. I haven't yet been able to reproduce this proble…

  16. Test failing on v3.18.0.2 but was not failing in v.3.17.0.2

    [quote=Dinesh;12635]Tested and it works with v3.19, thank you for the quick turnaround, really appreciated.[/quote] You're welcome :) Thanks for your patience!

  17. Test failing on v3.18.0.2 but was not failing in v.3.17.0.2

    [url=https://www.ncrunch.net/download]v3.19 is now available for download[/url].

  18. Test failing on v3.18.0.2 but was not failing in v.3.17.0.2

    Got it! This one really had me perplexed ... The problem is caused by a regression in v3.18. NCrunch is now incorrectly turning on the MSFakes/Intellitrace profiler when running tests. Most of the time this is harmless, but it looks like the code you've described has a compatibility issue with…

  19. Supported vs2017 versions?

    Hi, The problem you've referenced (GH-8073) is present for all versions of Visual Studio, unfortunately. The PR behind this issue was submitted to a component within the ASP.NET MVC project space to address a very specific compatibility issue with that component. Basically, it's a new part of A…

  20. Test failing on v3.18.0.2 but was not failing in v.3.17.0.2

    Thanks, I've managed to produce the result you're seeing now. For some reason, when I created a test project, it defaulted to .NET Core 2.1... This gave me a very different result. I'm digging deep into the problem now and will let you know as soon as I have more information.