logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Raath" <raa...@gmail.com>
Subject Re: .Net v2 support
Date Thu, 30 Mar 2006 06:37:53 GMT
I use it quite happily with version 2.0 "out of the box".

On 3/30/06, Morten Andersen <morten@vianett.no> wrote:
> .NET 1 components is also complient with .NET 2. If you want to, just
> use the compiled .NET 1.1 version from the website.
>
> I was running the v1.1 on v2.0 for a while until I recently upgraded to
> a version compiled for 2.0. Both work grate :)
>
> Best Regards
> *Morten Andersen*
> Developer
> Vianett AS <http://www.vianett.no/> | morten@vianett.no
> <mailto:morten@vianett.no> | Office: +47 69 20 69 74
> <callto://+4769206974> | Skype: mortander <callto://mortander>
>
>
>
> Thomas, Cord wrote:
> > As you point out - quick review of archives finds answer - you can
> > download latest source from cvs, set compile directive to .net2 (it's
> > called something else - see source) and it works.
> >
> >
> >> -----Original Message-----
> >> From: Young, Jason (GE Indust, GE Fanuc) [mailto:Jason.Young@ge.com]
> >> Sent: Wednesday, March 29, 2006 2:36 PM
> >> To: Log4NET User
> >> Subject: RE: .Net v2 support
> >>
> >> This gets asked very very often on this list.  I just use the
> >> current version, and it works fine.  I've heard of others
> >> that have changed some code, and got it to compile under 2.0.
> >>  I'm not sure what the point is.
> >> Anyone care to shed some light on that?
> >>
> >> -----Original Message-----
> >> From: Sylvain St-Germain [mailto:sylvain@macadamian.com]
> >> Sent: Wednesday, March 29, 2006 4:32 PM
> >> To: log4net-user@logging.apache.org
> >> Subject: .Net v2 support
> >>
> >> Hi,
> >>
> >> Are there plans for Log4Net to support .Net V2?
> >> If so, any idea when that might happen?
> >>
> >> Regards,
> >> Sylvain.
> >>
> >>
> >>
> >
> > --------------------
> >
> > This email message is for the sole use of the intended recipient(s) and
> > may contain privileged information. Any unauthorized review, use,
> > disclosure or distribution is prohibited. If you are not the intended
> > recipient, please contact the sender by reply email and destroy all copies
> > of the original message.
> >
> >
> >
> >
>

Mime
View raw message