Regardless of the importance of logging to your app, the fact that it's very easy to do basic logging with .net puts using an application block for that in question.
-----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Frans Bouma Sent: Thursday, March 31, 2005 5:02 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Enterprise Library - Poor Performance > Frans Bouma wrote: > > > It's very little work to do your own logging or > data-access? > > Perhaps in a 2-form 3 table project, but not in large scale > > applications with hundreds of tables and thousands of classes. > > OK. Point well taken, Frans. There may be a place for these > things, but in the smaller-scale projects I usually work on, > they do just what I said: cause more trouble than they're > worth. Notice how I said "I avoid...". I will continue to > do so until I'm on a project that I think would actually > benefit from it. > > Easy now, Frans :) ok :P I agree that small(er) projects do not always benefit from the fact that a lot of functionality is added to them through generic libraries, as in: why bother adding logging if no-one will look at the logs anyway. FB =================================== 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
