I would like to ask what issues people are seeing with the 4.0 runtime.
I have done, admittedly, a less than exhaustive test and had no
problems.
--
Roy Chastain
I would love to see a new release with the current code and all
fixes/enhancements built-in. There are a couple of changes in the
change database that I would like to have, but I have never been able to
use the tools to apply them to the current codebase.
After that is completed, a new 2.x releas
Ich werde ab 03.05.2010 nicht im Büro sein. Ich kehre zurück am
12.05.2010.
I am currently not in the office.
Wichtige Meldungen bitte an:
Important Mails to:
urs.kueh...@pago.ch
You're right. But for now I would leave out the generics. It is likely more
urgent that log4net works with .NET 4.0 right now because a lot of people
(like us) plan a UI rewrite with XAML in the next few months. I sense this
as the main stream of .NET in the near future.
> -Original Message---
On 2010-05-03, Ron Grabowski wrote:
> I just read that nant has a new release candidate out that supports
> .NET 4.0. Someone may want to try running that against the code base
> as that's how the final releases are built.
I ran the beta1 on NAnt 0.90 against log4net's build file in the root
dir
On 2010-05-03, Dominik Psenner wrote:
> But as long there are no breaking API changes needed to get log4net running
> with .net4.0 I would not target it as a major release, but more or less a
> 1.4.x.
Ron talked about taking advantage of generics in the API which would be
a breaking change. Oth
Good news that maybe something is moving on. My last note regarding .net 4.0
support was never answered and just resides somewhere in the history of
February (see:
http://mail-archives.apache.org/mod_mbox/logging-log4net-dev/201002.mbox/%3C
bc2abb510f3f405f9be041b89be06...@alpin.local%3e ).
I agre
