Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

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

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

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

  4. The OutputPath property is not set for project

    Thanks! Will take a look.

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

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

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

  8. 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 :)

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

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

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

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

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

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

  15. Tests are not recognized

    The best choice would be to [url=http://twitter.com/remcomulder]follow me on twitter[/url] - 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…

  16. Crunch crashes on every project.

    Sorry - this might seem like a stupid question .. but do you have v2.0 of the .NET framework installed?

  17. Crunch crashes on every project.

    Ok - I have a theory about what is happening here ... this appears to be an assembly resolution issue. The key variable here seems to be something in your environment that is causing different behaviour in assembly resolution compared with other environments NCrunch is tested in. Which exact ver…

  18. Crunch crashes on every project.

    That does help. Which plug-ins are you using right now? (other than Resharper EAP). Also ... have you tried using the Bug Report option in the menu? This will send through a log file that can help with tracking it down.

  19. The OutputPath property is not set for project

    I'd say that this is definitely likely to cause you problems. Try adjusting this to be a path relative to the project file you're building, and see if this helps. You may also need to use the [url=https://www.ncrunch.net/documentation/reference_project-configuration_overview]AdditionalFilesToInc…

  20. Crunch crashes on every project.

    Sorry for being vague :) There's a configuration option called 'InstrumentAssembly'. You can find it by going to NCrunch->Configuration then selecting one of your projects. I'm wondering if turning this off will get rid of the problem (if it does, then it must be the IL manipulation that causes t…