Menu
▾
▴
Re: [Netcommon-developer] Common.Logging - EntLib
|
From: Mark P. <Mar...@sp...> - 2009-01-15 16:12:51
|
I mean download on some site other than sourceforge, likely www.springframework.net/downloads/netcommon Mark > -----Original Message----- > From: Erich Eichinger [mailto:eei...@gm...] > Sent: Thursday, January 15, 2009 11:09 AM > To: 'Peter A. Kirk'; net...@li... > Subject: Re: [Netcommon-developer] Common.Logging - EntLib > > hmm. Just saw, that some unit tests implement ILog to capture output... > I'll > check this out to make migration easier and ping back here > > Redirection unfort. won't work as I just notice, because you are using > a > different key... > > stay tuned, > Erich > > -----Original Message----- > From: Peter A. Kirk [mailto:pk...@al...] > Sent: Donnerstag, 15. Jänner 2009 14:43 > To: net...@li... > Subject: Re: [Netcommon-developer] Common.Logging - EntLib > > Hi again. > > Just FYI, it is not such a simple matter to rebuild Spring against the > Common.Logging.dll rebuilt from the latest Common.Logging code > checkout. > > This is due to the fact that Spring provides an implementation of > Common.Logging.ILog, and this interface has some extra methods (eg. > TraceFormat, InfoFormat) in the latest code which were not included in > 1.2.0.0 code which Spring implements. (So one would also need to add > extra > methods to Spring's code...) > > So I'll try the binding-redirect. > > Thanks, > Peter > > > > -----Original Message----- > > From: Erich Eichinger [mailto:Eri...@sp...] > > Sent: 14. januar 2009 22:58 > > To: Peter A. Kirk; net...@li... > > Subject: RE: Common.Logging - EntLib > > > > Hi, > > > > you can safely use assembly version redirection > > (http://msdn.microsoft.com/en-us/library/7wd6ex19.aspx) to > > force Spring.NET to use the new version - the next version of > > Common.Logging (version number is TBD) is guaranteed to be > > binary compatible with 1.2. > > > > Another option is to simply rebuild the Spring.NET sources > > against the new assembly. > > > > hth, > > Erich > > > > -----Original Message----- > > From: Peter A. Kirk [mailto:pk...@al...] > > Sent: Mittwoch, 14. Jänner 2009 22:56 > > To: Erich Eichinger; net...@li... > > Subject: RE: Common.Logging - EntLib > > > > Thanks - I have tried to rebuild the sources, and have > > successfully generated the new Entlib41 assembly. So I can > > get this to work fine in my application - except in an > > application which uses Spring.net, because it is apparently > > built against common.logging version 1.2.0, which means it > > fails against the new dll I have built... > > > > > > > > > -----Original Message----- > > > From: Erich Eichinger [mailto:Eri...@sp...] > > > Sent: 14. januar 2009 12:44 > > > To: Peter A. Kirk; net...@li... > > > Subject: RE: Common.Logging - EntLib > > > > > > Hi Peter, > > > > > > If you're not afraid of compiling the sources yourself, you > > > find already everything in the trunk. Just check out the > > > resolved issues to see, what has happened since 1.2. > > > Not sure when we're going to make the next official release, > > > because there are some unsolved discussions about the > > > extended design of the ILog interface. If you want to take a > > > look into it, I'd be happy to receive your (and everybody > > > else's) feedback! > > > > > > cheers, > > > Erich > > > > > > -----Original Message----- > > > From: Peter A. Kirk [mailto:pk...@al...] > > > Sent: Mittwoch, 14. Jänner 2009 11:34 > > > To: net...@li... > > > Subject: [Netcommon-developer] Common.Logging - EntLib > > > > > > Hi > > > > > > I was really happy to discover "common logging", as our customers > > > normally use either Log4Net or Enterprise Library Logging - > > > so it would > > > be great to simply be able to select this via configuration. > > > > > > I was wondering though if "common logging" will be updated to > > > use EntLib > > > 4.1? The current release is for 3.1. > > > > > > Thanks, > > > Peter > > > > > > -------------------------------------------------------------- > > > ---------------- > > > This SF.net email is sponsored by: > > > SourcForge Community > > > SourceForge wants to tell your story. > > > http://p.sf.net/sfu/sf-spreadtheword > > > _______________________________________________ > > > Netcommon-developer mailing list > > > Net...@li... > > > https://lists.sourceforge.net/lists/listinfo/netcommon-developer > > > > > > > ----------------------------------------------------------------------- > ----- > -- > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Netcommon-developer mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/netcommon-developer > > > ----------------------------------------------------------------------- > ------- > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Netcommon-developer mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/netcommon-developer |