Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

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

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

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

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

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

  6. NChrunch and Dependancy Inject via Spring.Net

    Hi Heiko, Thanks for posting! You're correct in that it does look as though this is a problem caused by the runtime resolver. I'd really like to have a look at your sample solution if you can make it available. My knowledge of spring is very limited, but is it possible for you to supply your…

  7. no stack traces when test fails

    In this situation, the parent fixture will be the derived class you've created that is shown as the owner of the test inside the tree view. When you are inheriting from another fixture, you are effectively creating a new fixture with a different name that inherits many of the properties of the base…

  8. no stack traces when test fails

    Hi Tom, In this case, the test failed because its parent fixture failed on setup. If you choose the parent fixture in the tree view, it should show you the stack trace. NCrunch has a strong distinction between fixtures and tests, as mechanically they behave very differently. To show the stac…

  9. nCrunch doesn't build test project, as if it doesn't know about references

    No problem. Glad we figured it out :)

  10. nCrunch doesn't build test project, as if it doesn't know about references

    Thanks again. It looks as though the TeamAgile.XtUnit project isn't included in the same solution as your test project. Is this the case? Right now NCrunch has a known issue with building against references to projects outside the current solution. It's on the list of things to be addressed (a…

  11. nCrunch doesn't build test project, as if it doesn't know about references

    Thanks. As the bug report only contains a limited log capacity, I'm wondering if you might be able to give me a fresh capture. Would you be able to do a complete reset of NCrunch (disable/enable) then submit the report as soon as all the builds complete?

  12. NCrunch fails when building certain assemblies: PathTooLongException

    Hi Jay, Thanks for posting! This exception is being thrown from the project loader in NCrunch - so while changing the WorkspaceBasePath is definitely a good idea (and should be done for a project like this), know that this issue will occur before NCrunch goes to construct workspaces. You can p…

  13. nCrunch doesn't build test project, as if it doesn't know about references

    Excellent thank you! I've had a look through the bug report and it seems that something really strange is going on with NCrunch's resolution of the assemblies you have in the target\dev\x86\checked\ directory. Would you be able to show me how these files are being included in your build? (i.e. c…

  14. nCrunch doesn't build test project, as if it doesn't know about references

    Hi Tom - Thanks for reporting this issue. Would you be able to submit a bug report using the 'NCrunch' menu as soon as this issue occurs? It looks like a resolution problem inside the engine. Cheers, Remco

  15. Code Coverage percentage report on NCrunch

    Hi Asha, Thanks for posting. A number of people have requested this feature and it is on the list to be implemented in a future release. Cheers, Remco

  16. TestCase attribute with ">" fails to run

    Hi, thanks for reporting this problem. v1.36b (due for release before Christmas) has completely rewired the NUnit integration around test cases and has this problem resolved, so hopefully you won't need to deal with it for long. Cheers, Remco

  17. Conflict with MSTest: x64 vs. AnyCPU

    Hi Malte, Thanks for reporting this. A few people have been experiencing this problem and it's considered a high priority fix for 1.36b. Cheers, Remco

  18. Silverlight Support

    Hi Andrew - Thanks for letting me know about this tool - I wasn't previously aware of it and it looks very interesting. I'll keep it in mind :) Cheers, Remco

  19. Where does it host?

    It looks as though something in your tests project is causing the lines reporting the PDB file to be out of alignment with NCrunch's code model. Is this a codebase you're able to share? I'd really like to see what's different about this test project.

  20. Where does it host?

    Thanks for posting the details. I'll take a look at the bug report and get back to you.