Kian, A lot of people (especially those who work for large companies) have not made the switch to .NET 2.0 yet. At my company we've just started discussions about putting .NET on some of our virtual machines. It will be quite some time (several months) before its deployed company wide.
I glanced at the change log on for the log4net folder and saw that people started commited changes for .NET 2.0 in November. It hasn't been ignored. Its my understanding that the code in SVN compiles with little or no warnings under .NET 2.0. Instead of criticizing the volunteers who work on log4net in their free time, perhaps you could post to the dev list and describe what still needs to be fixed in order for the source in SVN to compile under .NET 2.0 without warnings. Better yet, write some patches to help close some JIRA issues. --- Kian Torabli <[EMAIL PROTECTED]> wrote: > To all those who asked about log4net availability on the .NET > Framework > 2.0: it was easy enough to compile it, took me less than two hours to > > adapt the code and test it. > > If you do not want to do the same chore yourself, I'll be happy to > provide the updated sources, just drop me an e-mail. > > IMPORTANT note: It will work for the Full Framework 2.0, not the > Compact > Framework, which I do not work with. > > To you guys from Apache: I am quite dissatisfied, to say the least, > with > your handling of log4net. Since you took over from sourceforge, there > > were no more final releases and as you can see from the many requests > > for 2.0, you do not seem to (be able to?) keep up to the required > speed > at all. Why not give this useful gadget back to the developer > community? > > - Kian >
