Q:

How should I handle logging when I create libraries for others? 

All.  I am creating some libraries for other teams in my company.  They all have different logging mechanisms.  I want to provide trace information of what my libraries are doing.  What should I to achieve this?  Thanks

A:

Use the built in Trace mechanism and document the fact. 
This way, all they need to do is configure tracing and they can log. 

A:

I would actually suggest using the newer TraceSource class, as recommended by the BCL Team during early .NET 2.0 development.   This adds some additional bells and whistles like the ability to name sources independently of one another and handle configuration through app.config files.