Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Support for NUnit's ISolutionBuilder and TestSuite

    Ok - try this build: [url=http://downloads.ncrunch.net/NCrunch_VS2012_1.45.0.14.msi]VS2012[/url] [url=http://downloads.ncrunch.net/NCrunch_VS2010_1.45.0.14.msi]VS2010[/url] [url=http://downloads.ncrunch.net/NCrunch_VS2008_1.45.0.14.msi]VS2008[/url] It's an experimental build, but hopefully i…

  2. NCrunch Build Fails with XUnit on VS2010

    It looks as though the Nuget package for AutoFixture is rigged with this deliberately to ensure that you're binding to its version of Xunit. Most probably this was done by the author to limit the potential for cross version issues with this framework. Although I don't know much about the inner wor…

  3. Disable while debugging

    Hi, thanks for posting! There isn't a feature in NCrunch that is specific to this, although I may be able to suggest better ways in which this could be handled so you don't need to deal with frustrating collisions. When you say 'debugging', do you mean by running your application with a debugg…

  4. Unable to find sn.exe for signing an instrumented assembly

    Hi Sam, That's great to hear. I'll see that the fix goes in with the next minor release. Normally this forum should send notifications from forum@ncrunch.net, although you aren't the first to mention this problem - I wonder if the feature or infrastructure is having issues of some kind. …

  5. NCrunch Build Fails with XUnit on VS2010

    Hi, thanks for sharing this issue. Giving this a quick try, I wasn't able to reproduce the issue. NCrunch's support for Xunit 1.9.1 actually works by redirecting to the 1.9.0 assembly that is packaged with its Gallio components - so it's definitely looking for the right file. The key question i…

  6. Unable to find sn.exe for signing an instrumented assembly

    Thanks Sam. I'll make sure the v7.0 is added to the list. NCrunch does also check for Wow6432Node, so I'm fairly certain the problem is just caused by the missed support for this particular version. Did adding one of the other registry keys allow you to work around the problem?

  7. Support for NUnit's ISolutionBuilder and TestSuite

    Thanks Fabio. The solution you sent was extremely useful in isolating the issue. NCrunch seems to be expecting all tests to be under a class that inherits from NUnitTestFixture, which of course would hardly ever be the case for custom NUnit addins. I'll see if I can arrange an experimental build …

  8. Support nunit [TestCase] attribute

    Hi, thanks for posting! I did look into doing this, as there would be clear value behind such a feature. However, the reason it hasn't been implemented is because it is really, really, really hard to do. Currently NCrunch finds code using debugging information emitted by the compiler. Custom a…

  9. Behavior around unused references different from MSTest

    Hi Jni, Thanks for sharing this issue. I can see how the behaviour of NCrunch in this situation could lead to builds failing, and a warning would be a useful thing to have. Because of the way the NCrunch test environment is built, I have a feeling that it will be very challenging to implement…

  10. Issue status

    Hi Wilhelm - Thanks for the feedback. There are plans in place to eventually introduce an issue tracker system that would include some integration with this. Everything that gets submitted through the bug reporter is read and considered anyway, so it's all useful information. If there's someth…

  11. How do I "Retrieve the LoaderExceptions property" please?

    Did the code coverage suppression or disabling of instrumentation make any difference? Also, can you confirm which language the project is developed in?

  12. How do I "Retrieve the LoaderExceptions property" please?

    This looks to be a bug in NCrunch's instrumentation. You may be able to work around it by marking out the offending code blocks with [url=http://www.ncrunch.net/documentation/concepts_code-coverage-suppression]code coverage suppression[/url] comments. An alternative is to disable instrumentation f…

  13. VS2012 update 2 seems to break NCrunch (on some systems)

    Thanks for sharing these details. My suspicion is that this is being caused somehow by the code under test. If you set a breakpoint on the first line of code of one of your tests (i.e. the opening brace), then choose to debug the test, does it hit the breakpoint? .. Or otherwise, are you making…

  14. How do I "Retrieve the LoaderExceptions property" please?

    Hi, Thanks for sharing this issue. I've made a note to introduce a future change to NCrunch to extend the error information to also include inner exception details. Meanwhile, we may need to deductively figure out why the CLR is failing to load your assembly. Do you have any static construct…

  15. VS2012 update 2 seems to break NCrunch (on some systems)

    Thanks for reporting this. I'm wondering if I could ask a few quick questions to help narrow this down: - Do you experience this problem with all solutions? Or just one in particular? - How often does the crash occur? Does it happen on every test cycle? - Do you notice the crash occurs severa…

  16. Lags in the editor after opening the Metrics window

    V2 is on target to be released in the fourth quarter of this year. The work to resolve the UI performance problems is already under way, so I can confirm that it will definitely be in the release :)

  17. Unable to find sn.exe for signing an instrumented assembly

    Hi Sam, It looks as though there's a hole in NCrunch's sn.exe resolution that doesn't cater for the configuration on your dev machine. Right now NCrunch looks in the following registry locations, checking for an 'InstallationFolder' value at: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SD…

  18. Problems with code analysis after upgrade

    Hi, thanks for sharing this issue. The 1.45 release included support for custom code analysis rule sets. Do you have a custom ruleset for this project or solution? I'm wondering if this may be the reason for this problem now surfacing (where it didn't with 1.44). The cause of the problem may…

  19. Lags in the editor after opening the Metrics window

    This makes sense. At the moment, NCrunch can't identify a 'hidden' status, as this is something under the control of Visual Studio. So unless the window is physically closed (via the X), NCrunch will continue to keep it up to date and drag down on the UI. Trying to limit the refresh actions to …

  20. MSpec with Behaviors does not 'Go to selected Test'

    I'll have a bit of a think around this to see if there's clean ways to solve this. There are other future feature areas NCrunch may explore that would open up opportunities here. Thanks for sharing the issue and the suggestions!