Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. NCrunch 1.36b and VB Imports Statement

    Ok - I have a feeling that this is due to an assembly referencing issue. Would you be able to submit a bug report after you have the build error?

  2. NCrunch run tests all the time

    NCrunch will automatically watch all files that are part of your solution. It then copies them out to a separate workspace, where they are built and the tests held within them are run. The only thing I can think of is if there is a test that is for some reason reaching out of the workspace and b…

  3. NCrunch run tests all the time

    Hi Archie, The only thing I can think of that could cause this is if you have a test that is somehow making changes to files that are being watched by NCrunch. For example, you may have a resource file generated from a test that exists as part of your solution. If you reference this file via …

  4. 1.36b Issue, might be with NuGet

    Hi Rangoric, thanks for posting! This appears to be a defect in NCrunch around its handling of configuration files and binding redirections. I'll ensure a fix for this is released as part of 1.37b (due before the end of the year). Removing the dotless.Core binding redirection in your Unit/Int…

  5. Problem building test assembly in 1.36b

    Hi Andrey, Thanks for sending through the bug report. I've noticed quite a few references to the custom targets file and it looks as though it's going into the workspace, so I think this may be an issue with the build itself rather than the workspacing. When your project fails to build, can y…

  6. 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?

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

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

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

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

  11. TestCase attribute messing up NCrunch entirely

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

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

  13. NCrunch fails to build

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

  14. ncrunch doesn't support nunit testcase

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

  15. InvalidProgramException on certain tests in solution

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

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

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

  18. 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. Unable to enable NCrunch for new install

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

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