NUnit core assembly referencing
Gary Evans <[email protected]> Sun, 13 Apr 2008 17:44:39 +0100
| Newsgroups | gmane.comp.windows.dotnet.nunit.devel |
|---|---|
| Message-ID | <[email protected]> |
Hiya, I tried loading my extensions, built against NUnit 2.4.6 in NUnit 2.4.7. I wasn't expecting it to work without tweaking, but I'm surprised that I couldn't tweak app.config to work without a rebuild of my extension. FileNotFound extensions were thrown from CoreExtensions.InstallAddins - the correct versions of the NUnit.Core.dll and NUnit.Core.Interfaces.dlls could not be found (was looking for 2.4.6.0). I inserted the following into NUnit gui's App.Config: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="NUnit.Core" publicKeyToken="96d09a1eb7f44a77"/> <bindingRedirect oldVersion="2.4.6.0" newVersion="2.4.7.0"/> <codeBase version="" href="file:///D:\FILES\GAZSTUFF\Rakija\NUnit2.4.7\NUnit-2.4.7-src\src\GuiRunner\nunit-gui-exe\bin\Debug2005\NUnitCore.dll"/> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="NUnit.Core.Interfaces" publicKeyToken="96d09a1eb7f44a77"/> <bindingRedirect oldVersion="2.4.6.0" newVersion="2.4.7.0"/> <codeBase version="" href="file:///D:\FILES\GAZSTUFF\Rakija\NUnit2.4.7\NUnit-2.4.7-src\src\GuiRunner\nunit-gui-exe\bin\Debug2005\NUnitCoreInterfaces.dll"/> </dependentAssembly> </assemblyBinding> This fixed the NUnit.Core problem, but not the NUnit.Core.Interfaces.dll problem (strangely!) Am I missing a simple step, or is there no way to get this to work without rebuilding against the later NUnit assemblies (which does work). It's likely that we'd want to reuse as much functionality as possible - we wouldn't want to duplicate too much code just to avoid this problem? (I'm thinking of deriving a ParameterizedTestCase, which would derive from NUnitTestCase, for instance) As an aside - would it be possible to show the user these file load exceptions somewhere - I knew what was wrong with my addin, but it might take a user by surprise if they couldn't see the actual errors - maybe the list of addins in the addins window which currently just shows "error" could have a link to click on showing the errors in instantiating the addin? Cheers, Gary _________________________________________________________________ Win 100’s of Virgin Experience days with BigSnapSearch.com http://www.bigsnapsearch.com ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ nunit-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nunit-developer