logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Haughton" <Neil.Haugh...@autoscribe.co.uk>
Subject RE: log4net in VS 2008 and .Net 3.5 environment?
Date Mon, 28 Jun 2010 14:32:50 GMT
We didn't have any  issues moving from .Net 2.0 to 3.5, with or without log4net. We are only
using 32 bit though (as most of our customers are still on that, to answer your question!).
Our toolset is VS2008 Team System.


Neil Haughton BSc MIET IEng(CEI)
Development Manager
Autoscribe Limited
Wellington House,
Riseley Business Park
Basingstoke Road, Riseley
Berkshire RG7 1NW
Office:   +44 (0) 118 984 0610
Fax:      +44 (0) 118 984 0611
Email:  neil.haughton@autoscribe.co.uk    Visit our website at: www.autoscribe.co.uk
Registered in Wales No. 1539748


The contents of this email are confidential and are intended solely for the use of the individual
or company to
whom it is addressed. If you have received this email in error then please accept our apology.
If this is the case
we would be obliged if you would contact the sender and then delete this email. Opinions expressed
in this email
are those of the individual and do not necessarily represent the opinions of Autoscribe Ltd.
Although this email
and any attachments are believed to be free of any virus no responsibility is accepted by
Autoscribe Ltd for any
loss or damage arising in any way from the receipt or use of this email or attachments.

-----Original Message-----
From: Jon Finley [mailto:jfinley@gksys1.hostpilot.com] 
Sent: 28 June 2010 14:35
To: Log4NET User
Subject: RE: log4net in VS 2008 and .Net 3.5 environment?

Thanks Michael,

Afraid that won't work for us (isn't the whole world now running 64 bit?? :-) ).  

I would really like to move our entire build to the 3.5 framework. 


-----Original Message-----
From: Michael Roberts [mailto:mikerobertswork@gmail.com] 
Sent: Friday, June 25, 2010 4:45 PM
To: Log4NET User
Subject: Re: log4net in VS 2008 and .Net 3.5 environment?

You can continue to use the Fx 2.0 version library when you move to Fx 3.5 as long as you
stay on 32 bit Windows.  (Things get trickier when you try to deploy on 64 bit Windows running
Fx 3.5.)

On my last project, we stuck with L4N 1.2.9 (2007?) during the move from VS 2K5/Fx 2.0 to
VS 2k8/Fx 3.5.

On Fri, Jun 25, 2010 at 5:59 PM, Jon Finley <jfinley@gksys1.hostpilot.com> wrote:

	Hi all,


	I know this has been previously discussed but I cannot figure out how to access the archives
of this list.


	We are currently running with VS 2005, .Net Framework 2.0, and log4net.  We are going to
upgrade our environment very soon to at least VS 2008 and .Net 3.5.  My question is, how have
others handled this change with log4net?  From the website, only the 2.0 framework is supported.






No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.830 / Virus Database: 271.1.1/2962 - Release Date: 06/25/10 00:35:00

View raw message