Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Recursive code being edited can sometimes cause NCrunch workers to die horriffically.

    Agreed. This is hard to fix because the CLR behaviour is to always terminate a process when it hits a stack overflow - there's no way to handle this exception. You'll notice other test runners behave the same way. I have some loose plans that may improve the experience around this in a later re…

    22 Feb 2012 08:03 UTC

  2. "Build in progress" for extended periods?

    Hi Jon - I've been getting this problem roughly once per day while working locally in the NCrunch solution, and I've narrowed it down to the code causing the problem. Thanks for your help in highlighting the issue, you can be sure I'll have a fix for it in 1.38b :) Cheers, Remco

    21 Feb 2012 21:09 UTC

  3. csproj imports

    Hi, thanks for posting about these issues. The postsharp problem is caused by a build dependency on a binary file that NCrunch isn't aware of. Right now NCrunch doesn't recognise the "UsingTask" MSBuild tag, so even though it is likely picking up the .targets import without problems, it isn't aw…

    20 Feb 2012 07:19 UTC

  4. "Build in progress" for extended periods?

    If there's an out of memory exception, then you're sure to get an explosion. If your system hangs with a build in progress, it's worth checking what's happening in the processing queue. If the queue itself doesn't show any data (or doesn't refresh), then this is the same issue shown above. If the…

    19 Feb 2012 20:52 UTC

  5. ETA of MSTest data driven tests?

    Hi John - Thanks for the suggestion. My original plan was to integrate with MSTest using Gallio, though I gave up after considerable effort when I found that the MSTest engine just didn't have enough hook points for NCrunch to work its magic. The problem isn't Gallio - it's MSTest :( Cheer…

    16 Feb 2012 21:09 UTC

  6. Code coverage for MVC app with IISExpress

    Hi Darren, Thanks for posting! At the moment, NCrunch isn't capable of analysing execution across multiple processes - though this is on the roadmap for releases further down the line :) Cheers, Remco

    16 Feb 2012 21:07 UTC

  7. New feature (cosmetical) request

    The hit boxes are deliberately made to be consistent across the marker types, so that the vertical line can still be easily selected. Is it only the X that you have trouble with? Are the other lines ok?

    16 Feb 2012 08:23 UTC

  8. v1.37b - Debug variables

    Thanks - I was having problems with reproducing this. This little piece of information is very helpful to me :)

    16 Feb 2012 08:23 UTC

  9. Add NCrunch.Framework to NuGet

    You are absolutely correct. And giving more space for people to create version inconsistencies will only make this worse... It may be the best solution would be to make the NCrunch.Framework code a bit smarter so that it can warn about version inconsistencies. I'll have a think about it.

    16 Feb 2012 08:22 UTC

  10. XUnit Assert.Equal message missing diagnostic info

    Thanks for reporting this. I'll take a look and will see what I can do.

    15 Feb 2012 20:34 UTC

  11. Minor display and mouse issues (high DPI settings)

    Hi Ylee, Thanks for reporting these - neither were on my radar. I'll see what I can do about getting them fixed. Cheers, Remco

    15 Feb 2012 09:41 UTC

  12. NCrunch Risk/Progress status as in NCrunch Tests

    Thanks for posting :) I have big plans in this area ... likely won't make it for 1.38, but it isn't far away :)

    15 Feb 2012 00:10 UTC

  13. NCrunch crashes when enabled

    Unfortunately it's the first time anyone has reported NCrunch failing at this particular point, so the log file isn't very verbose around the file that's actually causing the problem. From the stack trace I can establish that it's a reference to a non-code file that's written into the .proj file. …

    13 Feb 2012 21:00 UTC

  14. Add NCrunch.Framework to NuGet

    Hi Rory, Thanks for posting! I've been considering placing this DLL under nuget. My main concern is that it needs to be versioned alongside the installation of NCrunch consuming it, otherwise many of the features activated by it may not actually work. I'm glad your enjoying the tool :)

    13 Feb 2012 20:47 UTC

  15. "Build in progress" for extended periods?

    I've noticed this over the last week happening for me also. I did some investigation and it looks as though this is caused by a performance problem when making a large number of changes to a large source file. Basically, the individual changes (keystrokes) are bombarding the backend engine to wo…

    12 Feb 2012 21:16 UTC

  16. SetUp and TearDown methods not executed for NUnit tests?

    Hi Henri - Thanks for posting! You are correct in your understanding that these methods should run. Normally red dots indicate code that is covered by failing tests - have you customised your configuration? (not that this is a bad thing - I just want to confirm that it is actually code not cov…

    11 Feb 2012 23:44 UTC

  17. Can't examine symbols while using NCrunch to debug

    Hi, thanks for posting! Other users have also reported this, and though I haven't yet had a chance to look at it in detail my assumption is that it should be easy to reproduce. Thanks for taking the time to let me know about it - I can't promise a fix yet but I will definitely have a look :) …

    10 Feb 2012 21:54 UTC

  18. NCrunch crashes when enabled

    Hi, thanks for posting. This problem is being caused while NCrunch is trying to load one of your projects. There's something interesting/different about one of the file paths that's been specified in the project file and NCrunch is bugging out on it. Is this a project file that you've able to s…

    10 Feb 2012 21:52 UTC

  19. Larger font for Risk bar

    Oh, sorry.. I misunderstood :) Let me know if you have any more thoughts in this area. I'm keen to find ways of letting people work without needing to keep the Tests Window open, as not everyone has the screen space to do this.

    09 Feb 2012 20:27 UTC

  20. MonoDevelop support

    Thanks! At the moment, there are no plans to port to any IDE other than Visual Studio. This decision is purely because of the time and effort involved in maintaining integration points with so many tools and frameworks.

    09 Feb 2012 20:25 UTC