Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of nicko@neoworks.com designates
 80.168.17.114 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Interest in OpenNETCF (1.4)
Date: Sun, 13 Nov 2005 18:20:51 -0000
Message-ID: <DDEB64C8619AC64DBC074208B046611C7695CD@kronos.neoworks.co.uk>
Thread-Topic: Interest in OpenNETCF (1.4)
Thread-Index: AcXfADkEX88okJUBTF6KKKeYDa8j5wECoc+gAGNRLEAA98PMEA==
From: "Nicko Cadell" <nicko@neoworks.com>
To: "Log4NET Dev" <log4net-dev@logging.apache.org>

Kevin,

Sounds like you have made some good progress using the OpenNETCF
library. It looks like the main benefit is the additional appenders that
can be built for the Compact Framework.

Some of the changes to the Config namespace, in my opinion, are not as
significant improvements as to the Appenders. The
DefaultRepositorySelector and the attributes in the log4net.Config
namespace are not needed unless we can find some way to read assembly
level attributes (or make some sort of equivalent).

There are a few things that we may want to incorporate directly into the
log4net NETCF builds as we have done to provide support for Stack and
Guid. For example support for the WinCE equivalents to
GetCurrentProcess().Id and Environment.MachineName could be added to
SystemInfo.cs.

I don't want to make the log4net assembly dependant on the OpenNETCF
library for build simplicity and potential licensing issues. So I think
that the best solution is to make a new assembly, which does reference
the OpenNETCF library, with just the additional appenders. At the moment
I think the most we can do is to include this assembly (in source form)
as an example, i.e. it would go into examples\netcf\1.0\OpenNETCF.

If that is acceptable to you then the way to contribute code is to
create an issue in the log4net issue tracking system
(http://issues.apache.org/jira/browse/LOG4NET). Once the issue has been
created you can attach your patch file to the issue by selecting the
Attach file to this issue operation from the left hand menu. When
attaching your patch you must select the 'Grant license to ASF for
inclusion in ASF works' option.=20

More details here:
http://logging.apache.org/log4net/contributing.html#patch

Cheers,
Nicko

> -----Original Message-----
> From: Kevin O'Connor [mailto:koconnor@11.com]=20
> Sent: 08 November 2005 19:14
> To: Log4NET Dev
> Cc: Sean Going; Shawn Becker
> Subject: RE: Interest in OpenNETCF (1.4)
>=20
> Hi Nicko,
>=20
> I have finished a port of log4net that does use the OpenNETCF library.
> I have attached a description of what I have done, the files=20
> I edited (and a bit about why).  The library seems to work=20
> nicely in our framework. =20
>=20
> If this is of interest to the group, I'd be happy to submit=20
> the changes for review and inclusion.=20
>=20
> Please let me know the process for this.
>=20
> Kevin
>=20
> Kevin G O'Connor=20
> Eleven Technology     e: koconnor@11.com
> 45 Dunster St         p: 617.715.3031
> Cambridge, MA 02138   m: 617.834.1291
> http://www.11.com     f: 810.963.2708
>=20
> -----Original Message-----
> From: Nicko Cadell [mailto:nicko@neoworks.com]
> Sent: Sunday, November 06, 2005 3:02 PM
> To: Log4NET Dev
> Subject: RE: Interest in OpenNETCF (1.4)
>=20
> Hi Kevin,
>=20
> OpenNETCF isn't something that I was aware of, thanks for=20
> your email bringing it to our attention. It looks like the=20
> OpenNETCF library makes up for many of the shortfalls of the=20
> base NETCF platform.
>=20
> Many of the appenders in log4net which are not built for the=20
> NETCF platform could be built using the OpenNETCF library. =20
> These can be built into a separate assembly that links with=20
> the OpenNETCF library.
>=20
> As far as I know there is none working on using the OpenNETCF=20
> library to build log4net appenders.
>=20
> Cheers,
> Nicko
>=20
> > -----Original Message-----
> > From: Kevin O'Connor [mailto:koconnor@11.com]
> > Sent: 01 November 2005 16:21
> > To: log4net-dev@logging.apache.org
> > Cc: Shawn Becker; Sean Going
> > Subject: Interest in OpenNETCF (1.4)
> >=20
> > Hello,
> > =20
> > I am currently working on a .NET compact framework system. =20
> > We are making use of OpenNETCF Smart Device Framework (v=20
> 1.4).  I was=20
> > looking at the log4net project as a potential logging=20
> utility for this
>=20
> > system. The OpenNETCF SDF provides support for several areas of the=20
> > full .NET framework that are not part of the compact=20
> framework in the=20
> > area of logging (the OpenNETCF.Diagnostics namespace).
> > =20
> > I did a quick search of the dev list archives and did not find a=20
> > reference to OpenNETCF.  I am curious if there is anyone=20
> working on an
>=20
> > implementation of log4net using OpenNETCF SDF, and if not=20
> if there is=20
> > any interest in having it done.
> > =20
> > Kevin
> > =20
> > Kevin G O'Connor 	  =09
> > Eleven Technology	 ?e: koconnor@11.com=09
> > 45 Dunster St	 *p: 617.715.3031=09
> > Cambridge, MA 02138	 (m: 617.834.1291=09
> > http://www.11.com <http://www.11.com/> 	 *f: 617.876.3704=09
> >=20
> >=20
> >=20
> > =20
> >=20
>=20