Hi, What is the future of Log4Net? I mean is there any development or enhancements happening or only in support phase?
Warm Regards, Shrikanth Nanjunda Rao. From: Walden H. Leverich [mailto:[email protected]] Sent: Tuesday, July 05, 2011 10:18 PM To: Log4NET Dev Subject: RE: Query on the new release of Log4Net You are correct, you can download the source and just build it against the 4.0 framework. But the 2.0 DLLs work fine in a 4.0 application so it's not all that important actually. And since a build against the 4.0 framework wouldn't work on a 2.0, 3.0, 3.5 machine it doesn't make a ton of sense to be on the bleeding edge here. However, the one thing we can't do is build a _signed_ copy of the DLL (well, at least not signed with Log4Net's key, we could use our own) so if you have a requirement to put it in the GAC then you need it signed. -Walden -- Walden H Leverich III Tech Software & BEC - IRBManager (516) 627-3800 x3051 [email protected]<mailto:[email protected]> http://www.TechSoftInc.com<http://www.techsoftinc.com/> http://www.IRBManager.com<http://www.irbmanager.com/> Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) From: NanjundaRao, Shrikanth IN BLR SISL [mailto:[email protected]] Sent: Tuesday, July 05, 2011 6:32 AM To: '[email protected]' Subject: Query on the new release of Log4Net Hi, I am analyzing different open source loggers which can be used for the purpose of logging in our new application. I could see that there has not been a release of Log4Net in the last few years. The version 1.2.10 is compiled in Dot Net framework 2.0. With the latest version of Dot Net framework 4.0 in the market, and enhanced versions coming up, wouldn't it be a better approach to give a new release with the upgraded version. I believe I can download the source code, compile the same and distribute it on the production machines. In this case, am I going against licensing terms? I would like the former approach of getting the new Log4Net dll built in the latest Dot Net version. Hoping to get a response. Warm Regards, Shrikanth Nanjunda Rao. ________________________________ Important notice: This e-mail and any attachment there to contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank You. ________________________________ Important notice: This e-mail and any attachment there to contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank You.
