How do addon writers deal with NUnit versions?

Hi,

about eighteen months ago I've taken over the maintenance of
XMLUnit[1], which provides JUnit and NUnit extensions to test XML.  In
the beginning I focused on the Java part since this was where most of
the only bug reports and enhancement requests existed (and because
unlike the .NET version I used the Java version myself).

A few months ago I did a maintenance release of XMLUnit.NET which I
compiled against NUnit 2.4.6 (since that was the latest release back
then).  As far as I know this means that people using the XMLUnit.NET
binary can't use any other version of nunit.framework.dll (since this
is strongly named) - if anybody can correct me here, I'll be happy[2].

Prior to that release XMLUnit.NET had been compiled against much older
versions of NUnit (before the DLL has been strongly named) and things
just worked.

I certainly don't want to track NUnit releases with new releases of
XMLUnit, and I guess other addons are in a similar situation.  How do
you deal with this?  Tell your users to rebuild from source (this is
what I advised the bug reporter to do) or is there anything else I
could do?

Cheers

        Stefan

[1] http://xmlunit.sf.net/

[2] I've tried some tricks with binding redirects but they don't seem
to work when the Tests.*dll*.config file is used.

-- 
http://stefan.samaflost.de/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/