Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. NCrunch.Framework.ExclusivelyUses is not CLSCompliant

    Thanks for raising this. At first glance I don't see why the NCrunch.Framework assembly couldn't be made CLSCompliant. I'll take a look and see if its possible. Cheers, Remco

    23 Jan 2014 10:12 UTC

  2. [TestFixtureSetUp] runs twice with [TestCase] and [Test]

    Hi, thanks for posting! The behaviour of NCrunch will be slightly different in running this test compared with other test runners - although it isn't different quite in the way you may think it is. Because NCrunch executes tests in batches, it tends to make multiple calls into a test process t…

    23 Jan 2014 03:34 UTC

  3. Unicode issues

    I'm hoping to fix this in a minor release in V2. V1 is being wound down at the moment as the V2 RTM is very close.

    22 Jan 2014 09:07 UTC

  4. Unicode issues

    Thanks. This would be the same issue tied back to bugs in the richedit control. We really need to get rid of this thing. The fact that it appeared for you after Windows updates is particularly interesting. I wonder if this could have been an update related to the Russian language pack? Regard…

    21 Jan 2014 23:38 UTC

  5. NCrunch 2.3 Beta: Slow F# testing under VS2013 Update 1

    Hi, Thanks for sharing this issue. With the update still very new, I haven't yet had a chance to try it out, but this does sound like a build performance issue in the MS toolset. Do you notice unusually long build times with other project types also? (i.e. C#, VB.NET). Unfortunately NCrunch ca…

    21 Jan 2014 21:15 UTC

  6. The use of the Windows namespace is reserved

    Hi Lee - I'm wondering if you could check something for me. After NCrunch has failed to build your projects, can you try the following? - Right click on the failed build, choose Advanced->Browse to workspace - Find the generated .proj file inside the workspace for this project - Open a co…

    21 Jan 2014 20:55 UTC

  7. Unicode issues

    Hi! Sorry, I'm wondering if you could clarify the issue you've just had come up. Is this the issue with the Tests Window showing incorrect text, or is it the issue related to build errors being shown in the wrong language? Thanks, Remco

    21 Jan 2014 10:41 UTC

  8. GridNode cannot find sn.exe

    I think the problem here is that the latest version of NCrunch doesn't take consideration of machines that have only v4.5.1 of the .NET framework tools installed, but not v4.0. This should be an easy fix from the NCrunch side. Your copying of the file is the correct workaround that I would other…

    21 Jan 2014 04:11 UTC

  9. VStudio2012 freeze with NCrunch "stuck in build"

    My suspicion is that this was caused by a thread safety issue. I'll have a look at this from the NCrunch side, as there may be something I can do about it. Thanks for reporting it. I'm curious about the lag you're receiving in your IDE while running NCrunch. I have observed before IDE sluggish…

    20 Jan 2014 21:46 UTC

  10. VStudio2012 freeze with NCrunch "stuck in build"

    Hi, Thanks for sharing the stack trace ... You did well digging this up and correlating it with the lag. Did VS become completely unresponsive for the whole 20 minutes? Or did it just run really slow? Is this happening for you consistently? The rough edge with this issue is that because…

    20 Jan 2014 09:32 UTC

  11. Usability issue with MSpec tests when showing coverage only for selected assertion

    Thanks for sharing this. Mechanically, MSpec actually runs all the individual 'It' cases together - it is impossible to separate them .. which is quite different from other test frameworks, so I'm actually inclined to agree with you on this. I'll need to have a think about what the correct appro…

    18 Jan 2014 00:47 UTC

  12. Add local machine to the Distributed Processing window

    Hi Yang - Great idea. I particularly like the checkboxes. I'll need to have a look to see how I could implement this. Thanks for the suggestion.

    17 Jan 2014 22:43 UTC

  13. does not exist in the current context

    Sadly not. All test frameworks work with the same compiler and instrumentation, so they all have the same problem. The only way I'm aware of that can reduce the impact of this is if you try to avoid placing logic within methods that make use of await/yield. For example, moving the assertions ab…

    17 Jan 2014 22:41 UTC

  14. How to show Chinese in Tests... window

    Hi, thanks for reporting this. I'll take a look and will see what I can do :) Cheers, Remco

    17 Jan 2014 22:36 UTC

  15. Usability issue with navigating to MSpec test which use behaviors

    Hi, thank for sharing this issue. I agree with you. The navigation to tests, especially in this situation, is not ideal. I'll try to explain why. NCrunch itself is a language agnostic tool that extracts its test location and code coverage data using the debugging information generated by the…

    17 Jan 2014 22:36 UTC

  16. Usability issue with MSpec tests when showing coverage only for selected assertion

    Hi, thanks for posting! The code coverage for the DotIt method isn't shown when you choose to isolate coverage for the test, as this method is covered only by the fixture and not by the test. You'll find that if you were to add additional specs/testmethods to this class, the DoIt method would on…

    17 Jan 2014 22:28 UTC

  17. Building issue with Fody on grid node

    Thanks for the sample solution. I've managed to make this work by including 'packages\Virtuosity.Fody.1.19.5.0\**.*' using the Additional Files For Grid Processing configuration setting. I've also just noticed this setting is undocumented. I'll get that fixed :)

    17 Jan 2014 11:44 UTC

  18. Building issue with Fody on grid node

    Hi Yang - It's been a little while since I've looked at Frody, but I vaguely remember that it required references going back to the original solution location in order to work correctly. In theory, such a thing should be possible on a grid node. The grid nodes replicate the entire solution to…

    17 Jan 2014 11:39 UTC

  19. Using NCrunch v2 restarts build all the time when using Distributed Proccessing

    I've heard some reports of build/test spinners getting stuck perpetually when using the distributed processing, although to date no one has managed to pin down a way to reproduce it. In theory, the engine should drop all knowledge of remote processing when the connection to a remote machine has bee…

    16 Jan 2014 12:06 UTC

  20. Using NCrunch v2 switching between Visual Studio 2012 and 2013 removes GridNodeAddresses

    Great - thanks for the fast response. V1 doesn't know anything about the server list in the config file, so it would just nuke it. In case you do need to run both versions side-by-side, it is possible to store the servers in NCrunch's solution configuration file if you add the servers as being spe…

    16 Jan 2014 11:40 UTC