Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. DLLs Copied to project(s) root directory

    Hi Gareth - Unfortunately I've still had no luck in reproducing this issue consistently, but I can give you some advice on how to find out which project is making use of the contents in the references folder. There are a couple of quick ways you can do this - 1. Examine the NCrunch workspac…

  2. License Issue

    If the above steps don't solve the issue, try the following: 1. Open up VS/NCrunch, go to the license details dialog 2. Select 'Use evaluation license', click OK 3. Restart the IDE 4. Enter your license details 5. Close down the IDE, then clear out the contents of your current user 'temp'…

  3. Unknown constant type build failure

    Thanks, that narrows it down to the build itself (rather than NCrunch manipulation). As it can be quite tough to troubleshoot an issue like this without source code to recreate it, I hope you don't mind me bombarding you with a few questions ... - Which language are you working in? I.e. VB.NET…

  4. Unknown constant type build failure

    Hi, Thanks for posting! Does your build run correctly if you turn off the 'Instrument output assembly' setting for the project showing this error? Also - can you confirm which version of NCrunch you are running? Cheers, Remco

  5. xunit, ncrunch, VS2012

    Hi Chad - Thanks, I just saw the report come through! According to the log, it looks like NCrunch hasn't been enabled. Is there an 'Enable' option available to you under the 'NCrunch' menu?

  6. Bug? Test category isn't picked up when in Attribute but MSTest understands it

    Hi Paul - Thanks for posting! As NCrunch uses metadata to identify categories for tests (instead of dynamic invoke), this approach to defining custom attributes currently isn't supported. I'll ensure its in the backlog for a future release. Cheers, Remco

  7. xunit, ncrunch, VS2012

    Hi, thanks for posting! As far as I'm aware - this should be working normally. Can you describe the symptoms you're experiencing? Also, can you submit a bug report? Cheers, Remco

  8. DevExpress controls compatibility issues

    Hi, thanks for posting! This is unfortunately an ugly side effect of Visual Studio's plugin approach. The plugins share the same application domain, which prevents two assemblies being loaded under the same name but with different versions. The ultimate solution is for NCrunch to stop using…

  9. Local variables unavailable when debugging

    Hi John - This one is definitely still on the radar, although I've yet to find a way of fixing it. There is some kind of inference in the VS debugger that identifies compiler generated code blocks (such as yield), and NCrunch's instrumentation interferes with it. I'll keep looking, but its star…

  10. NCrunch Tests window is just showing as a big red X...

    Hi, This is caused by an exception being thrown very high up in the UI. Can you submit a bug report if you see this happen again? Also, have you managed to identify any pattern to it?

  11. Out of memory exception during build

    Good thinking :) I'll look into it!

  12. Run tests sequentially

    Hi, thanks for posting! Sequence dependent tests are, unfortunately, something you'll need to give up on if you're to make proper use of NCrunch. There's some more [url=http://www.ncrunch.net/documentation/considerations-and-constraints_test-atomicity]details about this in the documentation[/url…

  13. Out of memory exception during build

    A single assembly file with 2M lines of code is fairly unconventional, so I think it's quite a safe bet that the sheer size of the project is causing the memory problems. The best workaround I can suggest is basically what you've already done - setting the 'Instrument output assembly' setting to 'F…

  14. License Issue

    Something that may solve this problem is to go through the following steps after this has failed for you (and your license details are empty): 1. Shut down Visual Studio without entering your license details (cancel out of the license pane, or choose the evaluation license) 2. Load up Visual Stu…

  15. Out of memory exception during build

    As part of its instrumentation, NCrunch needs to load and dissect the built assembly in memory in order to manipulate it. On large assemblies, this can be a memory intensive process. Is this project being included in your solution as a project dependency, or as a referenced DLL? To ensure com…

  16. License Issue

    Hi, thanks for posting and for your purchase! This sounds like a state related issue and is probably related to the security configuration on your machine. Can you get in touch with me directly via the contact form? (http://www.ncrunch.net/Support/Contact) I'll help you to solve this issue of…

  17. Collapse/expand NCrunch Tests window items with arrow keys

    Hi, thanks for posting! This task is on the backlog :) Cheers, Remco

  18. "Clean" operations should remove ncrunch files (such as cache ...)

    I may be able to suggest something that can solve your immediate problem. 7z has a command line option (-x@) that allows you to specify an ignore file when creating a compression. The ignore file is in a fairly similar format to those used by many source control systems. You could add the NCrunch…

  19. Which NCrunch files/folders should be checked in and controlled by change control?

    A more sophisticated settings manager is in the plan :) Though you are correct - it is quite a large piece of work. It's also hard to implement without making the settings more confusing for less specialised cases .. so for now, NCrunch just uses fixed settings between the different areas (system/…

  20. NCrunch seems to get confused sometimes during frequent typing

    This is a long standing synchronisation issue that so far hasn't been fixed, largely because it is very rare and has never been reproduced in a situation where it could be analysed. If you can find a way to reproduce this issue, I'd be very eager to learn how. Otherwise, if you have it happen to y…