Hello, I have same issue as Jakub, some old projects depending on castle.core-log4net without clear path to upgrade. Why just not upgrade log4net in castle.core-log4net and make release? Exist users can continue use old package.
2013/10/31 Jakub Leśniak <kubal5...@gmail.com> > Hello, > thank you very much for your response. > > I would like to know the "long story" behind this. > > As far as my understaning goes: there's always the current version of the > package, so old users are unaffected - nuget can easily be forced to use > specific version of the package if the user wants to use Log4Net 1.2.10 for > some reason. > > There are two ways of doing the change - supporting only one version od > Log4Net i.e 1.2.11 or making it support all the newer versions - > i.e.version >=1.2.10. This way nuget can resolve the newest version > possible, but things can break in the future. > I don't know which strategy is better, but it seems that having a version > of this package for each version of Log4Net cannot do any harm. > > To sum up: what would be the reason not to upgrade? > > Thanks, > Jakub Leśniak > W dniu czwartek, 31 października 2013 13:02:39 UTC+1 użytkownik Krzysztof > Koźmic napisał: > >> Hey Jakub, >> >> sorry about the late response, I was on holidays. >> >> Long story short, there's no good solution to the problem, since either >> way (whether we upgrade the dependency or not) it'll break some users. >> >> For now I don't think we'll make the switch to latest log4net for the >> 'official' package, but quick search shows that someone already created an >> un-official one for the 'new' log4net >> >> https://www.nuget.org/**packages/Castle.Core-**log4net1211/<https://www.nuget.org/packages/Castle.Core-log4net1211/> >> >> I haven't used it, and I don't know the person who created the package, >> but it looks like it may solve your problem. >> >> >> cheers, >> Krzysztof >> >> On Monday, October 21, 2013 11:58:31 PM UTC+10, Jakub Leśniak wrote: >>> >>> Right now there are new official package versions for Log4Net. >>> http://www.nuget.org/packages/**log4net/<http://www.nuget.org/packages/log4net/> >>> >>> Is there any chance that dependency on version 1.2.10 of Log4Net can be >>> lifted to support i.e. 1.2.11 or 1.2.12 ? >>> >>> There are important features in those new versions like ability to use >>> connection string from web.config when using AdoNetAppender and some more. >>> I really would like to avoid creating and maitaining custom package if >>> updating this one is possible and seems be as simple as changing one line >>> in nuspec. I'm sure many people are waiting for this little change. >>> >>> If there is any help needed with this I can do whatever is needed. >>> >>> Thank you, >>> Jakub Leśniak >>> >>> W dniu wtorek, 25 września 2012 03:33:27 UTC+2 użytkownik Krzysztof >>> Koźmic napisał: >>>> >>>> There's no official package for the new log4net and at this time we >>>> have no plans to provide one. >>>> >>>> Feel free to build an unofficial one. >>>> >>>> The solution I would personally recommend is to use NLog. >>>> >>>> -- >>>> Krzysztof Kozmic >>>> >>>> On Tuesday, 25 September 2012 at 11:25 AM, JakeS wrote: >>>> >>>> I have a project that relies on both Castle.Core-log4net and >>>> Rhino.Servicebus. We started the project long ago, before nuget arrived on >>>> the scene. Our version of Castle Windsor is pretty severely outdated and >>>> we really should update to the latest stable release. We also have decided >>>> we should be using nuget to manage our references better. But it looks >>>> like the Castle.Core-log4net is referencing a specific (old?) version of >>>> log4net. >>>> >>>> Here's how to reproduce our issue. Start a new project. Use nuget to >>>> install Castle.Core-log4net and all its dependencies. Then use nuget to >>>> try and install Rhino.ServiceBus.Castle. The second installation will fail >>>> with the error "Unable to find a version of 'Castle.Core-log4net' that is >>>> compatible with 'log4net 2.0.0'." >>>> >>>> What can I do to resolve this issue? I've fought with this several >>>> times, trying to use binding redirects to sort things out, but the fact is >>>> that log4net DID make some minor changes between 1.2.10 and 1.2.11. >>>> >>>> Can I get a nuget package elsewhere? Or am I going to be forced to >>>> build castle from source after pointing it at the newer log4net? >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Castle Project Users" group. >>>> To view this discussion on the web visit https://groups.google.com/d/** >>>> msg/castle-project-users/-/**qiBTxVRr6IsJ<https://groups.google.com/d/msg/castle-project-users/-/qiBTxVRr6IsJ> >>>> . >>>> To post to this group, send email to castle-pro...@googlegroups.com**. >>>> To unsubscribe from this group, send email to castle-project-users+** >>>> unsubscr...@googlegroups.com. >>>> For more options, visit this group at http://groups.google.com/** >>>> group/castle-project-users?hl=**en<http://groups.google.com/group/castle-project-users?hl=en> >>>> . >>>> >>>> >>>> -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to castle-project-users+unsubscr...@googlegroups.com. > To post to this group, send email to castle-project-users@googlegroups.com > . > Visit this group at http://groups.google.com/group/castle-project-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/groups/opt_out.
