Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Exception when right clicking on processing queue

    This issue should be fixed in the 1.35b build that was released this morning.

  2. TestCaseSource attribute incorrectly requires TestCase attribute, not Test?

    This issue should be fixed in the 1.35b build that was released this morning.

  3. x86 vs x64 (Sqlite)

    For anyone interested, x64 support was introduced in the 1.35b build that was released this morning.

  4. Tests are not recognized

    The 1.35b release that went out this morning should introduce support for the above NUnit features. Please let me know how it goes :)

  5. Issue with NUnit SetUpFixtureAttribute

    This issue should be fixed in the 1.35b build that was released this morning.

  6. NUnit - Parameterised / Generic Test Fixtures show black indicators

    This issue should be fixed in the 1.35b build that was released this morning.

  7. System.UnauthorizedAccessException

    This issue should be fixed in the 1.35b build that was released this morning.

  8. Incorrectly reporting MSpec test results and icons stay black

    Hi Simon - I've had a go at fixing this issue in the 1.35b build that went out this morning. Are you interested in giving it a spin and letting me know if this works for you? Cheers, Remco

  9. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    This issue should be fixed in the 1.35b build that was released this morning.

  10. Version 1.35b not working?

    Thanks for raising this one - a few people have been hit with it at the same time. The issue is caused by the installer when upgrading from a previous version into 1.35b. To solve it, just uninstall NCrunch then reinstall 1.35b.. this should replace the taskrunner executables and all should be…

  11. NCrunch gets removed after VS 2010 Restarts

    I don't think that ReSharper would do this ... otherwise this forum would be exploding at the moment :) (Unless you have a very interesting development build of it). Something interesting we could try is to lock the NCrunch install directory in such a way as to bug out whatever is trying to dele…

  12. NCrunch gets removed after VS 2010 Restarts

    Hi Eric, Thanks for posting! This is a really weird problem. There isn't any code in NCrunch that would cause it to remove itself from the system (short of running the uninstaller, and from the behaviour you've described I don't think that's likely to be the case). Are you running a virus sc…

  13. problem with app.config file

    Ahh.. are you using named attribute parameters anywhere within your test? There is a known problem in this area that I'm working on at the moment :)

  14. problem with app.config file

    Ok - I don't think this is a problem related to your configuration ... something else is going on. Is the test ignored in the Tests Window? Or does it show with a green tick?

  15. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    I've introduced a fix in 1.35b for the read-only file locks, so I think this should sort out the problem for you. I'll drop a note as soon as the build goes out the door. Meanwhile, hitting the reset button should cause NCrunch to throw out the workspaces containing the locks and allow you to keep…

  16. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    I've had a look at this one in detail and I think it's because of read-only file locking problems. Are you using TFS?

  17. problem with app.config file

    Hi 4rchie, Thanks for posting. NCrunch should resolve your app.config file in the same way that other test runners do. Do you have any interesting build steps (i.e. a post build event?) that may be needed as part of preparing this config? Note that you can have a look at the workspace NCrunch …

  18. NullReferenceException building test project

    For anyone experiencing the above issue - I've had a look at this in detail and unfortunately it isn't an easy one to fix. One common cause of the issue stems from the use of COM interfaces in assemblies that NCrunch is attempting to instrument. If you are unlucky enough to have this problem, th…

  19. Set of Tests listed twice in the NCrunch Processing Queue

    Believe it or not, this is actually normal behaviour :) NCrunch will not remove tests from the queue while they are still executing, so if your tests were still running at the time your project was changed, then a new (often identical) task would be queued next to the old one. It's important t…

  20. System.UnauthorizedAccessException

    Thanks for reporting this one - I've had a couple of bug reports come through with a similar thing (I think one of them was yours). My best guess at the moment is that TFS is setting read-only locks on the files in your solution, and these read-only flags are being copied into the workspace by NCru…