Gallio v3.2 assemblies are completely incompatible with older versions (even v3.1)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a project that references Gallio v3.1 assemblies. Tests execute fine 
using TD.NET.
2. Replace the v3.1 assembly files with v3.2 assembly files (simply overwrite 
the files). The project's assembly references still contain the v3.1.x.x 
version number.
3. Tests no longer execute using TD.NET. Attempting to do so results in an 
error message in the output window similar to the one below.

What is the expected output? What do you see instead?

Expect to see normal "run test" output with test outcomes, etc.

Instead see an error like this (and no tests are executed):

------ Test started: Assembly: MyProject.Tests.dll ------

It looks like you're trying to execute a Gallio/MbUnit unit test.

For Gallio v3.0.6 build 787 / Gallio v3.1 build 313 or above
(recommended):
Please ensure that the directory containing your 'MbUnit.dll'
reference also contains Gallio's
test runner files ('MbUnit.dll.tdnet', 'TDNet\Gallio.TDNetRunner.dll',
'Gallio.dll' etc.)

For earlier versions:
You need to install Gallio (after TestDriven.Net) using its MSI
installer.

You can find Gallio downloads and support here:
http://www.gallio.org/ 

Please use labels and text to provide additional information.

See post related to the issue here:

http://groups.google.com/group/gallio-dev/browse_thread/thread/b07c8bffd2a581ee#

This post's issue seems like it might be related, too, although the 
circumstances are a bit different:

http://groups.google.com/group/gallio-dev/browse_thread/thread/3aa12801c9086b2e#

Original issue reported on code.google.com by justin.w...@gmail.com on 21 Aug 2010 at 6:00

[GoogleCodeExporter]

Further info:

I did look at the TD.NET registry entries when I was trying to upgrade my own 
projects from v3.1 to v3.2.

However, there were no version numbers or even anything related to the paths, 
names, versions, or anything else about the Gallio assemblies. And since I 
never installed Gallio, nor re-installed TD.NET, and was able to workaround the 
issue by updating my assembly references' version strings, it seems to me like 
the issue has something to do with Gallio itself. I would have thought that 
maybe the TD.NET code has some sort of built-in check, but I installed TD.NET 
before Gallio v3.0 was even released, so that seems unlikely and also points to 
the error message coming (somehow) from Gallio.

Original comment by justin.w...@gmail.com on 21 Aug 2010 at 6:12

[GoogleCodeExporter]

Here is the TD.NET registry info from my machine. It does contain some paths to 
some MbUnit v2.x files, but no paths, versions, etc. specific to Gallio or 
MbUnit v3.x.

Original comment by justin.w...@gmail.com on 21 Aug 2010 at 6:27

Attachments:

• TestDriven.NET.export.reg