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 containing references to files on different drives from the host solution, or perhaps references to files using UNC paths?

Is there any chance you could disable grid processing, set the engine to run tests manually, reset the engine, then immediately submit a bug report? The log file will then contain information that might help to identify the file reference involved.


Thanks!

Remco

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.

NCrunch's grid processing works by replicating your solution into a single directory space on the grid node. The replicated solution needs to be of an identical relative structure to the solution on the client machine, as it needs to be centrally managed and controlled according to the constraints configured on the grid node.

For a solution to be able to exist under the same directory as its projects, it must originate on the same drive on the client machine, as otherwise NCrunch won't be able to construct relative paths between the files to build a cohesive structure.

.. So the only way to be able to fix this would be for you to find a way to place the solution file on the same drive as the projects. Note that the solution doesn't need to be in the TFS-Workspace - it could simply be in a different directory on the same drive.

I've noted this down for review as I think there are better ways for NCrunch to handle this than to just kick up an internal error message.


Cheers,

Remco