Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. NullReferenceException on GridNode Server

    Thanks Lars. I've successfully recreated the problem and can confirm that it is caused by having the solution file on a different drive to the projects it contains. This is a bit of an issue for NCrunch, and I'm not sure if there is a way to fix it inside the product itself ... I'll explain why.…

    02 Dec 2014 20:56 UTC

  2. Ncrunch & Mef

    Hi, Thanks for sharing this issue. These tests are likely to be sequence/batch dependent. Because NCrunch is able to call into test runners multiple times within the same process (as part of its task batching), it is possible for the Bootstrapper code above to be run multiple times for the sa…

    02 Dec 2014 20:25 UTC

  3. NullReferenceException on GridNode Server

    Hi, Thanks for sharing this issue. My first thought is that there is something structurally unusual about your solution that NCrunch is having trouble handling. Most likely this is file path related. Does the problem appear for any other solutions? Does this solution have any projects conta…

    01 Dec 2014 20:42 UTC

  4. $(MSBuildThisFileDirectory) is not supported?

    Hi Yael, Unfortunately because of the location of the expression (Import condition), this eventually proved impossible to fix within NCrunch itself. I recommend using an alternative way to derive the import target directory. Note that in most cases it is still possible to configure NCrunch to…

    30 Nov 2014 20:12 UTC

  5. Customizing NCrunch distributed processing columns does not seem to persist

    Thanks for the heads up. I don't think these are being stored in the settings file ... and they should be. I'll see that this gets fixed.

    28 Nov 2014 10:24 UTC

  6. NCrunch pins tests which i haven't pinned before

    It's under the engine mode customisation window. Click the NCrunch menu, then go to Engine Modes, choose 'Customise Engine Modes'. Make sure you have your normal engine mode selected. There is a checkbox at the top of the details pane - 'Automatically pin newly discovered tests when using this en…

    27 Nov 2014 09:10 UTC

  7. NCrunch pins tests which i haven't pinned before

    Hi, thanks for sharing this. Is it possible you have the 'Pin new tests automatically' option turned on for your current engine mode?

    26 Nov 2014 22:33 UTC

  8. How to get a file copied to bin\Debug (/Release) for test projects?

    I've done some careful revision of this problem, and concluded that it likely isn't something that can be easily solved within NCrunch itself. NCrunch's build behaviour is very different to a standard build. It requires the assemblies to exist prior to their dependencies being resolved by NCrunc…

    25 Nov 2014 01:59 UTC

  9. Output version of console tool?

    Fair enough. I'll see if I can get it added :)

    24 Nov 2014 09:10 UTC

  10. Confusing test failure reporting with NCT.

    The parent fixture failure is being reported because of the child failure. Most test frameworks do this implicitly - where they don't, NCrunch will do it for them. A fixture is always considered to be failing if any of its child tests are failing. If a fixture itself is the source of the failure,…

    21 Nov 2014 20:32 UTC

  11. Troubleshoot [ProcessingFailed] with NCrunch Console Tool

    Internally, NCrunch has a concept of a 'Primary' build result. The Primary build result is considered to be the result of the first build to complete running for a particular version of the source code for a project. It is the only result that NCrunch considers when reporting build data in the l…

    21 Nov 2014 20:25 UTC

  12. Output version of console tool?

    Hi, Normally the console tool will emit the version number if you run it without parameters. It should be on the first line of text in the output. Is this what you're asking? Or are you looking for the version to be emitted when the tool is used with parameters also? Thanks! Remco

    21 Nov 2014 20:08 UTC

  13. Embedded Resource DLLs cause System.OutOfMemoryException

    Hi James, Unfortunately I haven't had any luck in reproducing this issue. I realise it's been a couple of months since you've reported it, so I'm not sure if this is still troubling you - but if it is, I'm wondering if setting the 'Build process CPU architecture' for this project to 'x64' in y…

    21 Nov 2014 05:23 UTC

  14. Distributed processing:incompatible versions

    Thanks. I think its related to the culture being used by the system account. I'll be including the fix in 2.11. Sorry for the trouble.

    20 Nov 2014 20:12 UTC

  15. Distributed processing:incompatible versions

    I believe the default culture is usually derived from the computers language/regional settings. One way you could be sure is by just running some test code on the machine and checking the value of System.Threading.Thread.CurrentThread.CurrentCulture. It looks to me like the code in NCrunch here …

    20 Nov 2014 09:54 UTC

  16. Distributed processing:incompatible versions

    Thanks for sending through the report. I noticed a very interesting difference between the contracts. When constructing the contracts, NCrunch will sort all types within the contract by their name. On the remote machine, the sorting seems to be different. For some reason, System.Byte is being pl…

    20 Nov 2014 09:38 UTC

  17. Windows 10 Technical Preview

    Hi, thanks for sharing this issue. I think it's related to the DPI scaling - though I wasn't aware that Windows 10 was involved .. this would make sense as it would explain how it has suddenly become a problem with no new NCrunch changes in this area :) I should have a fix for this out soon.

    20 Nov 2014 06:02 UTC

  18. Distributed processing:incompatible versions

    Hi, There have been some changes since you last reported this problem... these changes include adjustments to the bug reporter to include additional grid protocol information when connection attempts fail. If you can load up VS/NCrunch and get it to kick up this error, then straight away submit …

    19 Nov 2014 21:16 UTC

  19. Seat Licensing

    Hi Chris - Yes, absolutely. You can use the license on as many machines as you like, as long as you are the only one that uses it. If you ever leave the company, the company may transfer the license to someone else (which is something that isn't possible for a named user license).

    18 Nov 2014 20:45 UTC

  20. Support High DPI settings (MacBook Pro Retina and other high resolution laptops)

    Great, thanks! I'll see about getting this one fixed.

    18 Nov 2014 20:44 UTC