Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Event Logging
Message
From
02/07/2008 15:06:28
Timothy Bryan
Sharpline Consultants
Conroe, Texas, United States
 
 
To
All
General information
Forum:
ASP.NET
Category:
Object Oriented Programming
Title:
Event Logging
Miscellaneous
Thread ID:
01328368
Message ID:
01328368
Views:
45
Hi all,

I am creating a component library with code that currently is part of an application. I have an event logger project that is also used in our application and all events, messages, and exceptions are logged to an application log (text) file.

Since I am seperating all the code for this specific component to be used in multiple applications I would not have access to log exceptions from this component to the same log file. I could include the logger in the component and have a component specific log file but not sure if that would be all that helpful. My question is what do others do when they write a library with a public interface only to be used as a component in another application. Exceptions that I catch are the only thing that I am thinking of in this case. Do most just catch them and try to recover and not worry about logging them? I could raise a component error event so the application can worry about it. That seems reasonable. Any thoughts appreciated.
Tim
Timothy Bryan
Next
Reply
Map
View

Click here to load this message in the networking platform