tag:blogger.com,1999:blog-8263949408347549596.post6012620509255421220..comments2023-10-23T23:19:01.111+02:00Comments on Object-Oriented Software Development: Pathetic breaking change between log4net 1.2.10 and 1.2.11Wiktor Zychlahttp://www.blogger.com/profile/04420514974154487039noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-8263949408347549596.post-31409096065573541192015-07-07T12:05:29.020+02:002015-07-07T12:05:29.020+02:00This is a kind of old post, but just want to give ...This is a kind of old post, but just want to give some people a clue how to resolve this kind of problems.<br /><br />Basically you need to disassembly the old dll which references log4net 1.2.10, convert the code to MSIL, replace the publickey token in MANIFEST referencing log4net AND replace the signature of log4net Configure* method invocations to return ICollection. After those modifications compile the assembly back from MSIL code and voila! I did that using ILDASM + ILASM, which are both tools coming with Visual Studio.<br /><br />As far as I know there are no other compatibility issues except those mentioned.<br /><br />I have a success doing this to replace dependency on old log4net and moving to recent 1.2.13.0 version.Rasthttps://www.blogger.com/profile/12719633704906952212noreply@blogger.comtag:blogger.com,1999:blog-8263949408347549596.post-67640907006180377982013-02-12T21:12:05.312+01:002013-02-12T21:12:05.312+01:00@Wiktor: I think Dylan was having a go at the seco...@Wiktor: I think Dylan was having a go at the second 'Anonymous' comment, not you!<br /><br />Anyway, I completely agree with this article. I've just wasted several hours trying to get to the bottom of why I can't do a bindingRedirect between 1.2.10.0 and 1.2.11.0 till I found your article. Now, I'm going to have to back out log4net via NuGet and use a the previous version (1.2.10.0) as non-NuGet-controlled library. Not ideal.Neohttps://www.blogger.com/profile/04006786049710361344noreply@blogger.comtag:blogger.com,1999:blog-8263949408347549596.post-51989473506327076632013-01-08T11:02:51.778+01:002013-01-08T11:02:51.778+01:00@Dylan: I think you misinterpreted my article - I ...@Dylan: I think you misinterpreted my article - I blame log4net team for the mess they introduced with their own, quite basic mistake, a broken method contract between releases. Because of this, people got into real problems, I can't believe you miss that. And I am not going to switch to other technologies by myself, if I use A, B, C as third-party frameworks then their developers make the choice for me, THEY use log4net so do I. Problems start when A uses log4net 1.2.10 and B uses 1.2.11, there is really NO easy way to have both A and B in your code. And I don't care about Google, Samsung or Apple, I care about my code and my problems I got into because of the decision of someone from the log4net team.Wiktor Zychlahttps://www.blogger.com/profile/04420514974154487039noreply@blogger.comtag:blogger.com,1999:blog-8263949408347549596.post-17422877656482285232013-01-08T01:09:39.312+01:002013-01-08T01:09:39.312+01:00I love how the hater comes off with a tirade about...I love how the hater comes off with a tirade about a product made by someone else - then goes on to call other people "ignorant".<br /><br />The whole industry does the stuff you talk of. Last I checked Google/Samsung were the ones being sued for copying Apple's phone. As if you can give Java credit for ORM, Logging, Unit-Testing and Dependency Injection... lol.<br /><br />Why don't you go use a native Java bug logger if you hate MSFT related technologies?Anonymoushttps://www.blogger.com/profile/01463338099435510526noreply@blogger.comtag:blogger.com,1999:blog-8263949408347549596.post-828393516343652412012-11-27T13:57:21.201+01:002012-11-27T13:57:21.201+01:00There are two log4net 1.2.11 available for downloa...There are two log4net 1.2.11 available for download. One is signed with the old key and the other one with the new key. It is also described here: http://logging.apache.org/log4net/release/faq.html#two-snksNachbars Lumpihttps://www.blogger.com/profile/14625394345021266691noreply@blogger.comtag:blogger.com,1999:blog-8263949408347549596.post-48397584038234097142012-07-25T11:55:26.924+02:002012-07-25T11:55:26.924+02:00Something is in the air. Note however, that log4ne...Something is in the air. Note however, that log4net doesn't come from Microsoft. And unfortunately, the mentioned problem (migration from 1.2.10 to 1.2.11) doesn't have any safisfiable solutions.Wiktor Zychlahttps://www.blogger.com/profile/04420514974154487039noreply@blogger.comtag:blogger.com,1999:blog-8263949408347549596.post-39641076791546607932012-07-25T06:24:23.178+02:002012-07-25T06:24:23.178+02:00Keep in mind, it takes about 10 years for MS to ri...Keep in mind, it takes about 10 years for MS to rip-off Java technology like logging, ORM, unit-test, dependency injection u-name it. Microsoft is generally populated by ignorant Microsoft ass kissers, so to even recognize how pathetic they are (see current, previous versions of Windows phone) is blaspheme.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8263949408347549596.post-22384245498129949932012-03-09T18:58:27.205+01:002012-03-09T18:58:27.205+01:00Same problem here.
This missing "Configure&qu...Same problem here.<br />This missing "Configure" is a show stopper for me.<br />Downgrading to 1.2.10Anonymousnoreply@blogger.com