Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Coverage markers don't show in 1.40b

    I've heard reports that uninstalling and reinstalling NCrunch seems to resolve this problem. I'm currently working on introducing a proper fix for it.

  2. Does not work with Fody

    Hi Ylee, Most likely this is because the Fody binaries need to be included in the NCrunch workspace. Try adding a reference them using the 'Additional files to include' configuration setting, specifying a relative path.. for example: ..\Tools\Fody\**.*

  3. Updating NCrunch.Framework.dll

    Hi Kris, Yes - this has been suggested by a few people and it's something that I have been looking at :)

  4. Coverage markers don't show in 1.40b

    Hi Kay, Thanks for posting. I've had a few reports of this and I'm wondering if there may be a plugin clash here. I'm currently investigating.

  5. Build Failure, No Reason.

    Hi Davy, Thanks for posting! It looks NCrunch is having difficulty in constructing a workspace for one of your projects and is unable to report this error due to a defect. I've noted the defect down for a fix in a future revision. Meanwhile, let's see if we can find out why the workspace is f…

  6. No code coverage for references assembly.

    Would you be able to help by answering some of the questions below? This will help me to narrow down where the issue is: - Do you see any code coverage markers at all in the problematic project? (i.e. do you see any black markers?) - Are there errors of any kind showing in the Tests Window? - A…

  7. No Test Result / Code Coverage markers with 1.40 on 2012 RC

    You can turn on the 'Log to output window' option under the 'All Solutions' option inside the NCrunch configuration. When the log verbosity is set to Summary, NCrunch will only report critical information in the output window (i.e. exceptions). If you choose the NCrunch->Submit Bug Report option…

  8. No Test Result / Code Coverage markers with 1.40 on 2012 RC

    Hi, thanks for posting! Are you able to submit a bug report with this issue? It sounds like an exception is being thrown somewhere under the hood. Thanks! Remco

  9. MetricsExclusions saved as absolute paths

    Hi Marqus - Yes, sorry, I needed to include it as a separate property to simplify the upgrade process (since the file references are now in relative rather than absolute form). The data is stored at solution level more because of technical/design/ease-of-implementation reasons. NCrunch stores…

  10. new column in code coverage window

    For anyone interested, 1.40b has just been released .. including the above requested column in the Metrics view.

  11. Compile Errors Hyperlinking.

    Hi Marqus, I've just released 1.40b including several changes to the way that the click-through navigation works. Would you be able to give it a spin and let me know if the new build solves this problem? Thanks! Remco

  12. Failed to start in French

    For anyone interested, 1.40b has just been released with a fix for the above issue.

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

    For anyone interested, 1.40b (just released) includes a fix for this issue.

  14. Visual Studio 2010 hangs when adding a new item

    For anyone interested, Chris and I troubleshooted this offline from the forum and it was determined that NCrunch was causing performance problems during the resolution of certain referenced assemblies inside the Visual Studio process. 1.40b (just released) includes a fix that should resolve this pr…

  15. Skip unnecessary costly build steps (code analysis / code contracts static checker) when possible

    1.40b (just released) includes a split between the two code contracts settings. Static contract checking is now disabled by default, where dynamic contract checking is enabled by default. Hopefully this should make the behaviour of code contracts inside NCrunch more intuitive without sacrificing p…

  16. links to failing line of code acts odd when methods collapsed

    For anyone interested, 1.40b has just been released with a fix for the above issue.

  17. MetricsExclusions saved as absolute paths

    For anyone interested, 1.40b has just been released including the change requested above. Metrics exclusions should now be using relative paths (as opposed to absolute), and are sorted alphabetically for easier merging.

  18. Any plans to support NCrunch with enabled code contracts?

    For anyone interested, 1.40b has just been released including the above change.

  19. No corner spinner in VS 2012 RC

    For anyone interested, 1.40b has just been released including a fix for the above issue. NCrunch now shows a spinner in the corner of VS2012 :)

  20. nuget-installed ninject.extensions.factory fails under ncrunch

    For anyone interested, 1.40b has just been released including a change that sets the MSTest base directory to be equal to the build output directory (as described above). Hopefully this should help with resolving runtime referencing issues and align NCrunch more closely with other test runners.