Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Test Project build just stucks

    Ok - this means that the problem isn't caused by anything to do with the workspacing, which helps narrow things down considerably. Do you make use of any pre/post build events as part of the build for this project? If so, try turning on the run pre/post build event settings in your NCrunch proje…

  2. System.IO.FileNotFoundException : Could not load file or assembly

    Hi Rob - It looks to me like this test is making assumptions about the locations of assemblies required in the sandbox application domain. There is a section of the [url=https://www.ncrunch.net/documentation/troubleshooting_test-and-runtime-related-issues]test troubleshooting guide[/url] that ex…

  3. Support for running Moles (Fakes in 2012)

    Hi Rob, Thanks for posting! Right now NCrunch does not support Moles or Fakes, as both of these frameworks require a level of integration in order for them to properly operate. As Moles has been officially deprecated by Microsoft (replaced by Fakes), right now there are no plans to introduce …

  4. Test Project build just stucks

    Thanks for sending through the bug report. Would you be able to try the following for me? - Wait until the build has hung, then terminate lc.exe using task manager - Click the green 'check' in the NCrunch Tests Window to show the problematic project that's just been built - Right click on th…

  5. ccrewrite (0)#0: Rewrite aborted due to metadata errors. Check output window

    Nice working on identifying the indirect dependency. Most likely the code contracts rewriter was expecting the indirect dependency to exist in the same directory as the project being built, which would probably only be the case if the 'Copy referenced assemblies to workspace' setting was enabled. …

  6. Lines in unit tests given "not executed" color coding.

    Hi, thanks for posting! Something that often creates much configuration when people are using NCrunch is the difference between what I like to call 'logical' test coverage and 'physical' test coverage. Logical test coverage basically describes code that could normally be expected to be execute…

  7. Debugging tests that require an external dll

    Hi Kaleb, Thanks for the detailed analysis of the issue. Differing CPU architectures have a history of causing problems with test runners, as it can sometimes be difficult to establish what is the correct behaviour in setting up the test environment. The 'Use CPU architecture' configuration opt…

  8. Test Project build just stucks

    Often the Processing Queue Window can give you more information about unexpected build errors and internal problems. After your build has hung/failed, do you see any information in the Processing Queue Window against the build task? Also - would you be able to submit a bug report? I may be able …

  9. Excessive shadow copies of solution assemblies

    Hi Bob, Nice analysis! I'll need to look deeper into this issue to find out how NCrunch is wrecking havoc with MSTest. My gut tells me this will be quite complicated to fix, so I'm afraid it may need to be included in a future release of NCrunch (or VS??). I can suggest a possible workaround…

  10. ccrewrite (0)#0: Rewrite aborted due to metadata errors. Check output window

    Hi, thanks for posting! Does the project build correctly in NCrunch if you turn off the 'Allow dynamic code contract checking' option in your NCrunch project-level configuration? What happens if you enable the 'Allow static code contract checking' option? When you built your project via the c…

  11. vbc.exe issue on build

    Are you making use of any assembly-level attributes as part of your project? To a key-file or so perhaps?

  12. Test Project build just stucks

    Thanks. Can you share any more details about the build failure? (i.e. error message?). Does the project make use of any additional build steps or frameworks (other than MSTest)?

  13. ReflectionOnlyAssemblyResolve error during build

    Done! Thanks again.

  14. Debugging tests that require an external dll

    Hi, thanks for posting! In some application domains, the GetAssemblies().Select(x => x.Location) code will cause the exception you've described to be thrown. I've updated the documentation with an adjustment to this to avoid referencing System.Reflection.Emit assemblies which often are responsib…

  15. Which Configuration doe NCrunch use for tests?

    Hi, thanks for posting! You can control the build configuration used by NCrunch by adjusting the project-level NCrunch configuration option, 'Use build configuration'. NCrunch will normally use the default build configuration specified in the .proj file if you don't supply one, so normally thi…

  16. ReflectionOnlyAssemblyResolve error during build

    Hi, thanks for posting! I'm glad you managed to find the cause of this issue. Because NCrunch runs builds via the command line tooling, it wouldn't be injecting an override for this property in the same way that Visual Studio does. I'll see what I can do about introducing an override for this i…

  17. Huge Memory usage

    Great to hear! I have heard reports that the build runners tend to progressively increase their memory utilisation over time on some solutions. If this happens to you, just kill the BuildHost EXEs and they should recycle and carry on. I have a task logged to look into what is causing the leak i…

  18. Huge Memory usage

    Hi Rammesses, Thanks for posting! Looking at the EXE names of the task runners, it looks as though you aren't making use of the new hosted task runners. Are you running the latest version of NCrunch? 1.40b includes some fixes specifically focused on reducing memory utilisation.

  19. Feature requests

    Hi, thanks for posting! This is an excellent list of suggestions. Much of what you've described is in the backlog already, but I do see a couple of new gems in there. Thanks for your help, I'll see what I can do. Cheers, Remco

  20. Build failed with "SpecificVersion=True"

    Hi, thanks for posting! At the moment NCrunch doesn't consider this option, so it will be stripped out of the assembly/project reference in the .proj file that NCrunch constructs in order to build your project. With the current version of NCrunch, I'm not sure of any way you can work around this…