This new version of log4net if quite problematic I'm afraid. They've released this version with different strong name (again) so as noted, it's impossible to do redirects if you have a library depending on different version. How about relying on Common.Logging instead? That way it would be possible to use log4net, NLog and Enterprise Library logging (*shivers*) just by changing provider. Quartz.NET and Spring.NET use Common.Logging for example. Common.Logging has kept the same public key and API is compatible between versions.
Cheers, -Marko On 27 tammi, 22:53, Corey Kaylor <[email protected]> wrote: > I have updated log4net in the latest nuget publish. > > On Wed, Jan 25, 2012 at 9:23 AM, Torkel Ödegaard > <[email protected]>wrote: > > > > > > > > > Hi, > > > Just thought I would notify you, if you are not already aware that due > > too a log4net nuget update on december 21st the Rhino Servicebus > > package is now broken. > > > When installing latest Rhino.ServiceBus nuget package you also get > > installed log4net 1.2.11. > > > Rhino ServiceBus / Rhino Queues 2.2.2 is compiled against log4net > > 1.2.10. Log4net 1.2.11 differ in PublicKeyToken so no assembly > > redirect will work. > > > The Rhino.Queues nuget package does specify a version for its log4net > > dependecy, that is why nuget will take the latest version. > > > Regards > > Torkel > > > -- > > You received this message because you are subscribed to the Google Groups > > "Rhino Tools Dev" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/rhino-tools-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
