OK, that very good information.
I see that the MS Logging Application Block (LAB) allows messages to be
routed based on Category and each message contains a collection of
name-value pairs of meta data.
What is the corresponding Log4Net technology? From what little I have seen,
messages are
I am not a log4net expert... so please consult others too and do your
own investigation.
:: Category vs. log4net filtering
- Category is a flat filter rule. log4net hierarchy is much more
powerful. for additional filtering on other attributes, add info to
the properties and/or stacks and
I worked at a financial firm a few years back before the Logging Application
Block existed.. Microsoft came to us and asked us what we wanted next from
them in the area of Application Blocks.. Logging was one of the choices in
their potential near term plans..
Everyone in the room, including
Hi everyone!
I want to configure log4net in order to use the same configuration file
(with the watch option active) in my n-tier application!
I have the following structure in my solution:
Website (as a web application project)
Business (as a class library project)
Data (as a class
For each project, reference the log4net dll and put the following line
in the assemblyInfo file:
[assembly: log4net.Config.XmlConfigurator(
ConfigFile=log4net.config,Watch=true )]
Now at the class level for each class add the following line to create
an instance of the
For each project, reference the log4net dll and put the following line
in the assemblyInfo file:
I agree with referencing the log4net.dll, but I don't think you need to
put the [assembly...] attribute in. At least not if the top-level
application (asp.net) does the configure through code. We
You are correct, there is no need to set the attribute in each assembly. The
top level assembly handles the configuration -- everyone else goes along for
the ride. We have a number of library assemblies that get used in different
applications (web app, web service, service), so we didn't want
Hi,
it was just my back of the envelope guess at total working set usage
when I was considering the one-static-logger-per-code-class approach,
which was new to me at the time.
this was my thinking...
10K code classes is definitely an upper limit, and 100-1000 is probably
the common range. I
