> Is there a way to solve our issue, maybe instructing TestDriven.Net to
> use a specific executable instead of the installed version?
In the next release of TestDriven.Net there will be support for zero
install test runners and side by side versions. The way this works is
a special file is places next to the framework assembly
('MbUnit.Framework.dll') that lets TestDriven.Net know where to find
an appropriate test runner.
The latest versions of MbUnit and xUnit will support this out of the
box. It is very easy to add support for this to MbUnit 2.x. Simply add
a file called 'nunit.framework.dll.tdnet' next to
'MbUnit.Framework.dll' with the following contents:
You can add this to the MbUnit 2.3 and 2.4 'bin' directories. Once
you've done this you have a 'zero install' version of MbUnit that you
can optionally check into version control. After that you won't need
to install MbUnit using the MSI installer for TestDriven.Net
integration to work!
I'll email you a link to a preview version of TestDriven.Net 2.24 with
this feature. If anyone else would like to try a pre-release version -
let me know. Otherwise it should be live in a week or so.