I used the data access application block in the first half of last year and found it much more difficult to use and very poorly documented as compared with writing custom data access code.
-----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Frans Bouma Sent: Thursday, March 31, 2005 4:26 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Enterprise Library - Poor Performance > Andrew Gayter wrote: > > > Generic solutions to common problems generally are always > going to be slower than bespoke/performance solutions. Please, OR back it up with facts, OR retract this kind of silly remarks. Generic code definitely isn't synonyme to slower code, why should it be? > EntLib sits in the space of > > providing common/generic services and does loads of > 'stuff'; which if > > you'd implemented exception/logging etc wouldn't necessarily do? > > Well said, Andrew. This is the reason I avoid these > one-size-fits-all solutions from MS (or anyone, for that > matter). Not only do they not perform as well as custom > code, but they almost always cause more trouble than they're > worth in terms of learning curve and the pile of dlls I have > to reference and ship. It's very little work to do your own > Exception Handling, Logging, Data Access, etc. and it'll be a > much better fit for your app. 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. Ever implemented a fine grained tracing framework in your own code which gives trace listeners information? If you'd have, you would know that that takes way more effort than 'very little work' (even thinking through scenario's in which you would need which trace switches already takes more work than 'very little'). Not to mention data-access. The problem with libraries who do a lot for you is that the people using those libraries think that by just referencing the code it will all work as fast as it possibly can, completely forgetting that by using a piece of functionality with literarly thousands of options / functional elements, it is key to configure it right and set it up correctly. Suggesting to avoid that and 'do it yourself' with the reasoning that 'it is very little work' is IMHO simply telling the person a fairy tale. I won't comment in the quality of the enterprise library itself, as that's a complete different discussion. Frans =================================== 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
