Some things you may want to look into on this subject are WMI, and the aforementioned exception and logging app blocks. For an overview of where Microsoft is going with instrumentation, take a look at this :
http://msdn.microsoft.com/theshow/episode.aspx?xml=theshow/en/episode052/manifest.xml Interesting stuff, IMO, and I have to agree with the sentiment that logging, exception handling, and instrumentation should be part of your original design and not an afterthought. -------------- Original message -------------- > >> From what I can see from the help files, this trace stuff is just a fancy > > way of writing to data to a file (if that's the listener I choose) if a > flag is set and I can't see any advantage of it over standard logging to a > file if a flag is set. I assume I'm wrong because I can't see MS spending > a lot of time on this for no reason. So what am I missing? << > > You probably didn't look very closely. The listeners add a level of > indirection. Take a look at the docs and the interfaces available for them. > > > You can write to Trace but redirect the output to one of the built in > listeners such as a text file or event log. You can implement your own > listener to perform special processing or redirect the output elsewhere. > Finally, you can include multiple listeners at the same time, and all of > that can be configured via a config file. > > If you can say for sure that all you will ever need to do is write the data > to a file, this may be overkill, but if you ever think you will need the > ability to redirect it, you might want to look into it. > > =================================== > This list is hosted by DevelopMentor® http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
