Re: How do addon writers deal with NUnit versions?

Stefan Bodewig <[email protected]>
Newsgroups gmane.comp.windows.dotnet.nunit.user
Message-ID <[email protected]>
On Mon, 2 Jun 2008, Charlie Poole <[email protected]> wrote:

> Hi Stefan, 
> 
>> > Of course, this makes sense from the point of view of .NET, since
>> > XMLUnit might be using some method that exists in 2.4.6 but not
>> > 2.4.7. That's not very likely, so you could use a binding
>> > redirect at the user test level to force it to work.
>> 
>> I thought that would work, but it doesn't seem to be the case 
>> - or I may be using it the wrong way.
>> 
>> In my little test I placed a
>> 
>> <configuration>
>>   <runtime>
>>     <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
>>       <dependentAssemby>
>>         <assemblyIdentity name="nunit.framework" 
>> culture="neutral" publicKeyToken="96d09a1eb7f44a77"/>
>>         <bindingRedirect oldVersion="2.4.6.0"
>>         newVersion="2.4.7.0"/>
>>       </dependentAssemby>
>>     </assemblyBinding>
>>   </runtime>
>> </configuration>
> 
> I believe that should work, provided you put it in the right place.

That's what I thought.

See <http://stefan.samaflost.de/code/trivialtest2.zip>, this contains
a VS2008 solution with a trivial unit test, compiled DLLs and config
files - it doesn't work for me.

> If none of the above helps, I'd examine the fusion log next.

<http://stefan.samaflost.de/code/fusion.zip>.  This is the first time
I looked into a fusion log, so I may miss something obvious, but I
don't see anything suspicious.

Stefan

-------------------------------------------------------------------------
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/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.