I'd appreciate some guidance of the type of application that would
benefit from the use of the logging block -- which is itself built on
the Microsoft Enterprise Instrumentation framework.  I've read in many
places that the features of the logging block are potentially very
useful for "enterprise applications".  I guess I'm a little vague on how
people define that term.

As an example, I'm about to develop a Windows service that will run on
all 1000 workstations at my firm.  This service will be doing mostly
local work, but may occasionally interact with a remote, legacy DCOM
server, and perhaps a DBMS.  It will be multithreaded and likely listen
to control commands on a TCP/IP port.

Would this qualify as an "enterprise application".  Somehow I've gotten
the impression that when most people speak of these applications, they
are talking about server-side software.  Definitions aside, is this the
type of application that the logging solution is recommended for?

I'm already sold on the Exception Management Application Block and will
utilize those bits.  I'm just not sure whether I should integrate the
logging block when developing the service that I mentioned.  I'm
concerned that deploying it on all our workstations might be
problematic?  (If I do decide to use the logging block, I intend to use
its gateway to the Exception Management Application Block as
documented).  Or should I stick with the
System.Diagnostics.Trace.WriteLine(...)?

TIA