Couldn't this be fixed by creating multiple Castle.Services.Logging.Log4netIntegration libraries? I know it seems silly.. but kinda seems like the correct thing to do at this point... You have to treat a key change like that as if it is different library all together...
In my opinion, Log4net lost a lot of credibility when they changed their key.. but regardless... they are on version 1.2.13 and they are still producing 2 binaries with each build... That being said.. the newest build with the old key doesnt work anymore... they have made a change to their api so it seems that castle is pegged at version 1.2.10... On Friday, January 4, 2013 6:06:36 PM UTC-5, Chris Constantin wrote: > > Couldn't find such an unofficial package, so I just published one: > http://nuget.org/packages/Castle.Core-log4net1211 > > Cheers, > Chris > > On Monday, 6 August 2012 14:28:40 UTC-7, Krzysztof Koźmic wrote: >> >> Yeah, either way you're going to upset people. This is madness, and I'm >> not giving into it. >> >> That being said, feel free to provide an unofficial package for v1.2.11. >> >> -- >> Krzysztof Kozmic >> >> -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/castle-project-devel. For more options, visit https://groups.google.com/groups/opt_out.
