Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Installs themself as nCrunch.VSIntegration2010 in VS2012

    It's using the same components, so I guess this makes sense (though very undesirable!). I'm rewriting the installers right now, so I'll see if I can sort this out.

  2. VS2012 RC undocked editor becomes uneditable after ncrunch flyout

    Hi John, Thanks for reporting this issue. I noticed a number of changes to the way UI messages were being handled with the new VS2012 release, resulting in a few issues similar to the one you've described. I had thought they were all fixed - though I don't think I tested this particular case. …

  3. Path.GetFullPath not returning consistently with MsTest or resharper test runners

    Hi John, In VS2010, MSTest would always set the current directory to be equal to the MSTest 'Out' directory. NCrunch was modelled from this behaviour, though most likely not all test runners actually do this. It looks as though the behaviour in this area has changed with the VS2012 release. …

  4. Coverage markers don't show in 1.40b

    I've managed to reproduce this issue and confirmed that it's a VS setup issue impacting adornment layers while plugins are being upgraded. I've posted some instructions next to the download link that should resolve the problem in case anyone else is hit by this. Thanks for reporting this!

  5. Path.GetFullPath not returning consistently with MsTest or resharper test runners

    Hi Johan, Thanks for posting! Can you share which version of NCrunch you are using to run this test? The version of NCrunch just released (1.40b) includes a change that should hopefully rectify the issue as you've described it. Cheers, Remco

  6. Build problems

    Hi, thanks for posting! Are you using any custom build frameworks or do you have any custom build steps? If you can submit a bug report after this issue occurs, I'll have a look through the log file to see if I can help find the cause. Thanks! Remco

  7. Coverage shows black when tests cover code

    Hi Kaleb, Thanks for sharing this code - your thoughtfulness made this problem much easier to diagnose. The _badPasswords and GetBadPasswords blocks of code are not being registered as covered because they are being physically invoked BEFORE NUnit actually reports any test as having begun exec…

  8. Error when calling unmanaged dll in 1.40b

    Hi Marqus, Thanks for reporting this problem. It looks like this is a marshalling problem of some kind that only surfaces in the new hosted task runner introduced with 1.40b. You can work around this problem by turning off the 'Use hosted task runner' option in your global NCrunch configurati…

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

    I've finally managed to reproduce this problem on my end. After adding an extra step to the [url=https://www.ncrunch.net/documentation/troubleshooting_missing-code-coverage]upgrade instructions[/url], the problem seems to have resolved itself. Give it a try if you have time, I'd really like to kno…

  10. Does not work with Fody

    If copying the all nuget files to your workspace is an issue, probably the best thing you can do would be to individually specify the Fody dependencies using wildcards, one on each line. For example: packages\PropertyChanging.Fody.1.12.0.0\**.* packages\SomethingElse.Fody.1.12.0.0\**.*

  11. Does not work with Fody

    Is this something that could be achieved with a post-build event? Pre/post build events are disabled by default in NCrunch, but you can easily switch them on if you need to apply extra logic to your build process. NCrunch itself doesn't really do any magic within your build process. It simply c…

  12. nCrunch.Host.x86.exe preventing devenv.exe from exiting normally

    Hi, thanks for posting! The nCrunch.Host process is something launched by the NCrunch VS Extension during shut down of VS. It is responsible for cleaning up any leftover workspaces created by NCrunch, as soon as the devenv.exe process has completely terminated. As such, this is actually the rev…

  13. Coverage markers don't show in 1.40b

    I've introduced a new revision of 1.40b to the download page including a speculative fix for this issue. I haven't yet reproduced it on my end, but hopefully the fix should resolve it. Please let me know if you see this issue again!

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

    I've introduced a new revision of 1.40b to the download page including a speculative fix for this issue. I haven't yet reproduced it on my end, but hopefully the fix should resolve it. Please let me know if you see this issue again!

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

    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.

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

  17. 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\**.*

  18. 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 :)

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

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