Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. 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…

    30 Aug 2012 00:26 UTC

  2. 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.

    30 Aug 2012 00:24 UTC

  3. 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 …

    29 Aug 2012 20:59 UTC

  4. 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 …

    29 Aug 2012 20:56 UTC

  5. 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

    28 Aug 2012 21:13 UTC

  6. 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 :) …

    28 Aug 2012 21:11 UTC

  7. 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…

    28 Aug 2012 21:05 UTC

  8. 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. …

    27 Aug 2012 21:09 UTC

  9. 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…

    27 Aug 2012 21:04 UTC

  10. System.NullReferenceException when running with isolator V7

    Excellent news! Thanks for sharing!

    25 Aug 2012 22:52 UTC

  11. 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…

    25 Aug 2012 22:50 UTC

  12. 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…

    25 Aug 2012 11:07 UTC

  13. 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 …

    24 Aug 2012 22:24 UTC

  14. 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

    24 Aug 2012 08:22 UTC

  15. 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…

    23 Aug 2012 22:06 UTC

  16. Build Errors Needs Details and New Window

    The issue you've described (no messages showing against build errors) is usually caused by an internal problem. I'd really like to learn more about this problem so that I can solve it properly. If you open up the Processing Queue Window and select the failed build in the list, is there any informa…

    22 Aug 2012 21:02 UTC

  17. Bug: NCrunch tries to build Modeling Projects

    Hi, thanks for posting and for making me aware of this issue. I'll note it down for a future fix. Have you tried using the 'Ignore this component completely' project-level option inside your NCrunch configuration (underneath 'General')? This should, in practice, remove NCrunch's knowledge of th…

    22 Aug 2012 07:59 UTC

  18. Change/Disable max execution time for tests

    NCrunch will automatically apply a timeout of 60 seconds to each test (by default). You can change this by adjusting the configuration on your test project, 'Default Test Timeout'. However, a better way to do this is to assign [url=https://www.ncrunch.net/documentation/concepts_test-timeouts]sen…

    21 Aug 2012 20:58 UTC

  19. T4 and assembly references

    Hi Alex, Something to watch out for is that the 'Copy referenced assemblies to workspace' setting only applies at individual project level, so if you haven't tried this already, make sure you try turning it on for all the projects in your solution (as this will make the NCrunch build more closely…

    21 Aug 2012 11:18 UTC

  20. ExclusivelyUsesAttribute on Test fixtures

    Hi, thanks for posting! Yes - The ExclusivelyUsesAttribute should work at fixture level, and it should also inherit through to derived tests. There is a known problem with NCrunch where sometimes if you add a new ExclusivelyUsesAttribute onto a base class that is in a different assembly from t…

    20 Aug 2012 20:53 UTC