Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. NCrunch 1.36b and VB Imports Statement

    Hi Sam, Thanks for posting. Does it make any difference if you turn off the IncludeStaticReferencesInWorkspace setting for the project exhibiting the build error?

    19 Dec 2011 22:58 UTC

  2. Problem building test assembly in 1.36b

    Hi, thanks for posting! Do you have any custom build steps for your project? Or you making use of any SDKs or build frameworks? It would be great if you could submit a bug report after your build error - this will help me to identify why this error is appearing. Thanks! Remco

    19 Dec 2011 22:54 UTC

  3. Donations?

    Hi Malte, Thanks for offering to support the project! At the moment I don't have anything set up to support donations or contributions, so I have the say that the best thing I could ask for would be that you help to spread the word and you continue to share any issues and ideas in this forum. N…

    19 Dec 2011 20:58 UTC

  4. Issues with NUnit TestCaseSource

    Good to hear! I'd be lying if I said that NUnit didn't put up a fight on this one, but persistence pays as always :) For the grouping, I was thinking that you may be able to reduce the number of test cases by finding common elements between them, then putting those common elements inside a singl…

    19 Dec 2011 08:59 UTC

  5. Issues with NUnit TestCaseSource

    Hi Jon, Thanks for providing the links to your working solution. This was enormously helpful for me in making some critical changes to the way the NUnit integration works for NCrunch 1.36b. 1.36b (just released) allows you to consume NUnit using dynamic analysis instead of static analysis. T…

    19 Dec 2011 08:19 UTC

  6. TestCase attribute messing up NCrunch entirely

    The fix for the above problem has now been released as part of 1.36b.

    19 Dec 2011 08:13 UTC

  7. NCrunch build fails when WPF project has a SplashScreen image.

    The fix for the above problem has now been released as part of 1.36b.

    19 Dec 2011 08:11 UTC

  8. NCrunch fails to build

    The fix for the above problem has now been released as part of 1.36b.

    19 Dec 2011 08:10 UTC

  9. ncrunch doesn't support nunit testcase

    The fix for the above problem has now been released as part of 1.36b.

    19 Dec 2011 08:09 UTC

  10. InvalidProgramException on certain tests in solution

    The fix for the above problem has now been released as part of 1.36b.

    19 Dec 2011 08:08 UTC

  11. NCrunch continually failing with "process cannot access the file"

    I've implemented a proper fix for this in 1.36b, which has just been released. Hopefully we won't see this one again!

    19 Dec 2011 08:08 UTC

  12. Conflict with MSTest: x64 vs. AnyCPU

    The fix for the above problem has now been released as part of 1.36b. Essentially, you can now control (through configuration) the processor architecture used by NCrunch's test environment. Please let me know if this solves the issue for you.

    19 Dec 2011 08:08 UTC

  13. NCrunch fails when building certain assemblies: PathTooLongException

    The fix for the above problem has now been released as part of 1.36b. Please let me know if this solves the problem for you.

    19 Dec 2011 08:07 UTC

  14. Unable to enable NCrunch for new install

    The fix for the above problem has now been released as part of 1.36b.

    19 Dec 2011 08:07 UTC

  15. No build output

    You may be able to solve this by [url=https://www.ncrunch.net/documentation/reference_global-configuration_overview]changing the base path for your NCrunch workspaces[/url]. Basically, you need to move the workspaces closer to the root of the disk. This will reduce the length of the file paths a…

    17 Dec 2011 03:49 UTC

  16. NCrunch fails when building certain assemblies: PathTooLongException

    Hi Jay, I've taken a deeper look at this, and it may be fixable. NCrunch 1.35b isn't efficiently using the entire path space of 260 characters - which means your path may be slightly under this limit but NCrunch is pushing it above. I've implemented a fix in 1.36b, and I think it would be good …

    16 Dec 2011 22:11 UTC

  17. Using NCrunch with JustMock

    Hi Thorsten - Thanks for posting! So far no support has been added for JustMock, though I believe this should be a simple process. I will see what I can do about adding it in a future release. I'm afraid I can't offer you a workaround as there is no configuration that can override the task run…

    16 Dec 2011 10:59 UTC

  18. No build output

    Usually if you have a build failure but no error, it means there's been an internal problem in NCrunch. The best thing you can do in this situation is go to have a look at the project in the processing queue. The queue will often have a much more physical view of the error. If you can copy/paste …

    16 Dec 2011 10:57 UTC

  19. no stack traces when test fails

    Gotcha. Yes - this is a bug. NCrunch doesn't deal with issues in SetUpFixtures too well because they can't associate with any individual test. The most intuitive way to handle them would be to write their results back into the project itself (as you've described). This is something I'll need to …

    15 Dec 2011 21:13 UTC

  20. NCrunch fails when building certain assemblies: PathTooLongException

    I wish I could offer you a fix, but I don't doubt that there will be many areas within NCrunch's engine where such a long path will cause problems. I'll make a note to improve the error message so it's more informative and will also give you the name of the problematic file. Cheers, Remco

    15 Dec 2011 21:10 UTC