Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. The OutputPath property is not set for project

    Hi Andrew, Thanks for sending through the log file. I can reproduce this problem consistently and can confirm that NCrunch has a compatibility issue with static libraries shared between projects. So far, NCrunch's support for C++ projects has been shallow and is quite limited. I do have some…

    23 May 2011 17:04 UTC

  2. Color blind friendly colors by default, please.

    Thanks for the heads up. This one is not obvious unless your colour blind I guess :) 1.31b (due out in the coming week) will have a wizard step that allows you to set the marker colours before you actually start using the program. I hope this will help to sort out the issue ... originally this …

    22 May 2011 17:10 UTC

  3. Optional "Run Tests only after Save"

    Some time ago I experimented with the [url=http://memory.dataram.com/products-and-services/software/ramdisk]DATARAM[/url] one and found it to work quite well for me. Results will probably vary depending upon your system I'm sure :) You can reduce your CPU consumption by keeping your [url=https:/…

    22 May 2011 17:07 UTC

  4. Run failed tests first?

    Yes it does. There is a weighting system inside the engine that takes into consideration: * Tests impacted by the changes you have made * Tests that are failing * Tests that run faster ... along with a few other lesser important factors :)

    22 May 2011 17:01 UTC

  5. Problem: Blocking Third-Party Assemblies with VS2010

    Absolutely :) This is definitely how the issue will be fixed. Right now NCrunch shadow copies everything else ... just not the referenced assemblies. There's no reason for them being special - just a question of time and effort :)

    22 May 2011 16:59 UTC

  6. Problem with NUnit TestCase attribute

    Thanks for the heads up on Theories - I'll need to look into this one as it still seems to be in an experimental state. At the moment, I have no plans to implement support for Inconclusive tests in the near future. This is largely because of the effort/payoff ratio behind this feature, but also …

    22 May 2011 16:56 UTC

  7. Optional "Run Tests only after Save"

    You're not the first person that's asked for this, so definitely I think it will need to be included at some stage. At the moment, you could set the system to run tests manually, though it will still run background builds (thus churning up your battery). Although I've never really tested NCrunch…

    21 May 2011 18:25 UTC

  8. Crunch crashes on every project.

    I have now confirmed 100% that this defect is surfaced only on machines with a German version of Windows installed. This does not impact machines that are running the English version of Windows configured to use the German language pack. A fix has been implemented in the upcoming 1.31b release d…

    19 May 2011 21:45 UTC

  9. The OutputPath property is not set for project

    Thanks! Will take a look.

    19 May 2011 18:56 UTC

  10. Crunch crashes on every project.

    Slieser - Are you running a German Windows 7? (as opposed to an English Windows 7 running in German). This may make all the difference..

    19 May 2011 17:02 UTC

  11. Interop.ActiveDS causes unreliable build in ncrunch

    The next time you see the SGEN failure, could you use the Submit Bug Report option in the dropdown menu? I'd like to have a look at the logfile to see what's going on. Cheers, Remco

    19 May 2011 11:25 UTC

  12. The OutputPath property is not set for project

    Nice going. Try introducing the Platform property as a element of an unconditional PropertyGroup inside the build script. This will be effectively the same as injecting it through the command line, and it should work with NCrunch.

    19 May 2011 06:28 UTC

  13. Problem: Blocking Third-Party Assemblies with VS2010

    NCrunch currently locks it's referenced assemblies with its background processes. This will likely change in a future version, but for now the easiest way around this is to just disable NCrunch when you go to delete the files. Closing down VS will work too - although that is a bit excessive :)

    19 May 2011 06:23 UTC

  14. Interop.ActiveDS causes unreliable build in ncrunch

    Is the Interop.ActiveDs assembly being referenced directly from the output directory of the location it's built from? This would make sense, as rebuilding the entire solution would update the file (and therefore NCrunch would grab a new reference to it). I have little knowledge about this assemb…

    18 May 2011 16:43 UTC

  15. NCrunch IPC issue

    Hi Rainer - Thanks for posting. This issue has been reporting by a few users now and I'm treating it as a priority fix for the next beta release next week. I'll let you know if I identify a workaround. Cheers, Remco

    18 May 2011 16:40 UTC

  16. Interop.ActiveDS causes unreliable build in ncrunch

    Are you able to give any more information about how the build is failing? I.e. the messages showing etc. Also, if you haven't already - it's worth having a look at [url=https://www.ncrunch.net/documentation/troubleshooting_project-build-issues]troubleshooting build issues[/url] in the wiki.

    18 May 2011 12:04 UTC

  17. Crunch crashes on every project.

    Ok - I think I may have a fix for this issue, though it is purely speculative as so far I haven't been able to reproduce it. 1.31b is on track for release next week .. would you be keen in giving this a try when it's kicked out? If it doesn't solve the assembly resolution issue, it should at lea…

    18 May 2011 08:16 UTC

  18. Tests in generic Test classes not recognized

    I have seen a similar problem around this to do with the inheritance of the InclusivelyUsesAttribute and ExclusivelyUsesAttribute ... didn't realise it would impact the test attributes also. I'll have a look into it.

    18 May 2011 06:25 UTC

  19. Bug: Double clicking "N/A" in the Risk/Progress Pane crashes VS 2010

    Yep. Looks like that happens for me too. Good catch - I'll see what I can do.

    18 May 2011 06:21 UTC

  20. Tests are not recognized

    The best choice would be to [dead link] - I make NCrunch announcements from there :) The product roadmap itself is quite variable and it depends on the experiences people have with the tool. The first priority at the moment is to ensure the tool will work across all environments.

    18 May 2011 06:19 UTC