Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. VS11 ShimNotSupportedException when using Shimming from Microsoft Fakes

    Hi Imi - Unfortunately there is no quick fix for this. Fakes relies on a custom profiler that will require considerable effort in order for NCrunch to integrate with it. A fix for this is still quite a way out. Sorry. Cheers, Remco

  2. Defaul argument makes NCrunch build fail

    Hi, thanks for sharing this issue! Right now NCrunch doesn't officially support working with Silverlight projects, although I've placed this issue on the backlog for review when Silverlight support is eventually added. An another note, this website will be getting a major upgrade soon. The is…

  3. System.Security.VerificationException: Operation could destabilize the runtime

    Hi Oliver, Right now NCrunch simply doesn't support working with partially trusted code (or code access security), as this adds a considerably complex dimension to its development and may not actually be possible with the way it works internally (more testing is required). I'd like to introduce …

  4. Bug? Feature Request? Multiple processing threads should not use the same workspace.

    Hi, thanks for posting! NCrunch can use the same workspace for multiple test runner processes, though it will never run multiple threads within the same process. The problem with creating a new workspace for every test runner is that this means ALL projects within the solution need to be built…

  5. NCrunch causes VS2008 to lock up for a while every single build

    Thanks. The specification of your machine is slightly better than the machine being used to develop NCrunch itself (which isn't a small solution), so I'm sure your hardware should normally be more than adequate for a good experience. Performance issues like this can often be tough to track down.…

  6. 1.41b: 'Additional files to include' not working?

    Thinking about what could cause this, another simpler way could be to simply change one of the boolean project configuration values to something else, then back again. This will cause NCrunch to create the .ncrunchproject file for the project you're updating and will have the same effect as copying…

  7. Build failure issue - 'Class1' does not contain a definition for 'Property2'

    Does it make any difference if you turn on the 'Copy Referenced Assemblies To Workspace' setting for all the projects in your solution? MS Test private accessors require this, and NCrunch should usually turn it on implicitly, though this doesn't seem to be working reliably in the current build.

  8. 1.41b: Post build step being run for vcxproj.

    Thanks for making me aware of this. The C++/CLI build events likely use a different configuration setting and need to be disabled differently. If this is causing you problems, try adding a Condition="$(NCrunch) == ''" attribute in the property representing them in the build file. I'll see what I …

  9. 1.41b: 'Additional files to include' not working?

    Hi, thanks for posting! There have been reports of this problem. It seems to be caused by a configuration sequencing issue that can be present if you try to edit the property before NCrunch has properly created the configuration. To work around it, try disabling and re-enabling NCrunch until …

  10. NCrunch causes VS2008 to lock up for a while every single build

    Sorry I just thought I'd also quickly check whether you've also experienced this problem while using NCrunch with other good sized solutions on your computer. This is quite an important factor in determining the source of the issue. Cheers, Remco

  11. Good Job NCrunch!

    Hi, Thanks for sharing your experience with NCrunch!!! It's great to hear it's been working so well for your team and that it's met with everyone's expectations internally. It's little posts like these that make my day and keep feeding me with the motivation to make NCrunch better and better :) …

  12. NCrunch causes VS2008 to lock up for a while every single build

    Hi Owen, Thanks for posting! Can you share any details about the computer you're running on? How many processor cores does it have? Is it a low-spec machine? If it's a multi-core machine, make sure you haven't accidentally assigned processor cores to BOTH NCrunch AND Visual Studio - as th…

  13. 64 Bits - Failed Tests

    Hi, thanks for posting! My suspicion is that you are using a test project that has been built with a target platform of AnyCPU, testing against another project (or referenced assembly) with a target platform of x64. This would work in MSTest if you have configured the MSTest runner to use x64. …

  14. static variables inside classes

    Hi, thanks for posting! NCrunch will never, ever, ever run multiple tests in parallel within the same execution process. It really is physically impossible with the current design. Based on your description, I think it could be worth checking the following: - Make sure that the log file name…

  15. System.NullReferenceException when running with isolator V7

    Excellent news! Thanks for sharing!

  16. Some Tests Fail - Possibly those that have a reference to a specific third party DLL

    If you're receiving different results from the test simply by running and rerunning the test in isolation, then this is almost certainly caused by a race condition or a state related issue. Examine the test carefully to see which resources it touches that exist outside the testing process (for ex…

  17. Some Tests Fail - Possibly those that have a reference to a specific third party DLL

    Inconsistent pass/fail can be a symptom of the following: * Race conditions in the test/code (particularly if the code is multi-threaded or cross-process) * Sequence dependency - for example, some tests may have been written with the accidental assumption of other tests being run before them (or n…

  18. Some Tests Fail - Possibly those that have a reference to a specific third party DLL

    Hi, thanks for posting! This looks like a runtime issue with the test, likely caused by NCrunch's [url=https://www.ncrunch.net/documentation/concepts_workspaces]workspacing[/url]. Cross-process tests often require a bit of extra configuration in order to work correctly under NCrunch, as NCrunch …

  19. 139b ... doesn't seem to honour machine.specifications.ignore attribute

    It's possible this could have been a synchronisation issue of some kind. Perhaps you added the ignore attribute and NCrunch didn't properly pick it up until the engine was reset. I guess there's no way to know now, but I'm glad it's working for you! Cheers, Remco

  20. 139b ... doesn't seem to honour machine.specifications.ignore attribute

    Hi, Thanks for posting! I just tried this use case locally and was unable to reproduce the problem (the test was ignored for me). Is there any extra complexity around this test that is not shown in your code snippet? Can you confirm that the ignore attribute you're using is Machine.Speci…