Please forgive the possible double email. I subscribed to the list last
week and got my confirmation mail. When I sent an email to the list
earlier today, I got a message back indicating that it was being held
pending moderator approval because it was by a non-member to a
members-only list. It might appear to be from a nonmember because I
used an old format (very abbreviated) work email address. Outgoing
emails are tagged with a newer format email address (full name plus full
company name). Anyway, I am sending the contents of that email inside
of this email (I have resubscribed with my new email address) to see if
I can see on the Common Infrastructure Libraries for .NET homepage at
SourceForge that the next scheduled release is "June". The page shows
that it was last updated on 5/4/09. The download page shows that
Common.Logging 2.0 was most recently updated in Feb 2010. Does that
mean that the next scheduled release is (was) June 2009?
Are the features listed on the homepage still the next features to be
implemented (partial trust, Azure, Silverlight, trace context support)?
I am currently looking at Common.Logging and SLF (slf.codeplex.com) as
possible solutions for insulating a new project from a specific logging
For some background, we will be targeting .NET 4.0 and higher (i.e. at
this point we don't expect to have a requirement to provide a lot of
legacy support). We expect to use a lot of Silverlight, WPF, and WCF,
so we would like to be able to log from any or all of these
environments. At this point, I anticipate that our primary usage of
something like Common.Logging or SLF (or something else) to be to
insulate our source from a dependency on a specific logging library. I
do not anticipate having to bridge between logging systems. Of course
that could change if we use a third party library/app that uses a
specific logging library. Right now we expect to use a static logging
manager (e.g. LogManager) rather than getting logger(s) by DI.
We are still pretty early in the design phase and are doing a lot of
research and prototyping. I am coming from a limited .NET background,
having spent the past 10+ years programming in COM and VB6.
Looking for any tips for particularly thorny issues related to logging
and Silverlight and WCF.
Thanks for any info regarding the next release of Common.Logging and
thanks for any tips that anyone is willing to share.