Menu
▾
▴
netcommon-developer
|
From: Peter A. K. <pk...@al...> - 2009-01-14 10:55:44
|
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 |
|
From: Erich E. <Eri...@sp...> - 2009-01-14 13:10:27
|
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 |
|
From: Peter A. K. <pk...@al...> - 2009-01-14 22:52:28
|
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 > |
|
From: Erich E. <Eri...@sp...> - 2009-01-14 22:32:00
|
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 > |
|
From: Peter A. K. <pk...@al...> - 2009-01-15 13:42:52
|
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 > > > |
|
From: Erich E. <eei...@gm...> - 2009-01-15 16:09:36
|
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 |
|
From: Mark P. <Mar...@sp...> - 2009-01-15 16:11:05
|
Hi, Ok, let me take one last look at the new methods to close this loop and we will make a release next week... 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 |
|
From: Mark P. <Mar...@sp...> - 2009-01-15 16:12:18
|
Erich, Can you make a local build and we'll post it up for download in the interim. Buyer beware clauses apply.... 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 |
|
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 |
|
From: Erich E. <eei...@gm...> - 2009-01-16 02:47:05
|
The signed preview build for the upcoming version 2.0 of Common.Logging is ready for download at <http://www.springframework.net/downloads/netcommon/> What's new? ----------- - added support for EntLib 4.1 logging - extended ILog interface now includes XXXFormat( string format, params object[] args ) signatures - leveraging lambdas, the ILog interface offers a new & safe way to write log statements: log.Debug( m=>m("value= {0}", obj.Value) ); this ensures, that the whole expression is only evaluated when LogLevel.Debug is enabled and thus saves you from writing if (log.IsDebugEnabled) { log.Debug("value={0}", obj.Value); } to avoid this overhead. Upgrading --------- All that's necessary for upgrading from 1.2 is copy the new assemblies in place and specifying a version redirect. Recompiling your application of course links your app to the new version w/o a redirect. 2.0 runtime (Common.Logging.dll) is fully binary backwards compatible. Note to implementors of the ILog interface: Due to the extensions, you need to extend your implementations as well. As an added benefit, 2.0 comes with some convenience classes, making it easy to implement your own log system integration. Check out AbstractLogger and AbstractSimpleLogger for more information. Spring.NET ---------- I removed the dependency of Spring and it's SPI implementation of ILog for testing purposes, thus compiling & testing the codebase against the new version is no issue anymore starting with the next nightly build of Spring.NET Give the new version a whirl and please send your feedback! enjoy, Erich |
|
From: Peter A. K. <pk...@al...> - 2009-01-16 08:58:06
|
Thanks a lot for that, guys! With your new common.logging.dll I can get my app to work with EntLib 4.1 and with Spring.net 1.1.2 (with an assembly redirection). /Peter > -----Original Message----- > From: Erich Eichinger [mailto:eei...@gm...] > Sent: 16. januar 2009 02:45 > To: net...@li... > Subject: [Netcommon-developer] Common.Logging v2.0 preview > ready for download > > The signed preview build for the upcoming version 2.0 of > Common.Logging is > ready for download at > > <http://www.springframework.net/downloads/netcommon/> > > What's new? > ----------- > - added support for EntLib 4.1 logging > - extended ILog interface now includes XXXFormat( string > format, params > object[] args ) signatures > - leveraging lambdas, the ILog interface offers a new & safe > way to write > log statements: > > log.Debug( m=>m("value= {0}", obj.Value) ); > > this ensures, that the whole expression is only evaluated when > LogLevel.Debug is enabled and thus saves > you from writing > > if (log.IsDebugEnabled) > { > log.Debug("value={0}", obj.Value); > } > > to avoid this overhead. > > > Upgrading > --------- > All that's necessary for upgrading from 1.2 is copy the new > assemblies in > place and specifying a version redirect. Recompiling your > application of > course links your app to the new version w/o a redirect. > 2.0 runtime (Common.Logging.dll) is fully binary backwards compatible. > > Note to implementors of the ILog interface: Due to the > extensions, you need > to extend your implementations as well. As an added benefit, > 2.0 comes with > some convenience classes, making it easy to implement your > own log system > integration. Check out AbstractLogger and > AbstractSimpleLogger for more > information. > > > Spring.NET > ---------- > I removed the dependency of Spring and it's SPI > implementation of ILog for > testing purposes, thus compiling & testing the codebase > against the new > version is no issue anymore starting with the next nightly build of > Spring.NET > > Give the new version a whirl and please send your feedback! > > enjoy, > Erich > > > > -------------------------------------------------------------- > ---------------- > 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 > |
|
From: Mark P. <Mar...@sp...> - 2009-01-14 15:04:37
|
Hi, Erich Eichinger has done this already, the code is in svn and we were planning to make a 2.0 release but it has been held up because I want to review the changes to the API. I'm almost convinced on the changes that Erich made... In anycase, is it possible in the meantime for you to check the code out of svn and do a build? You will need to generate your own private key to perform the build. Cheers, Mark > -----Original Message----- > From: Peter A. Kirk [mailto:pk...@al...] > Sent: Wednesday, January 14, 2009 5:34 AM > 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 |
|
From: Erich E. <eei...@gm...> - 2009-01-14 12:54:01
|
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 |
Thanks for helping keep SourceForge clean.
X