Are any of the other "Application Blocks" worth looking at (or definitely to be avoided)? I've been reading the docn (but not the code!) for the "User Interface Process" block, and it seems to have good goals -- it seems to offer the promise of writing only one set of "business logic" code and using it from within both a Web app and a WinForms app. However, it also seems to make what seems like very simple stuff involve a moderate amount of work. (If it had design-time wizards that built e.g. the XML file that lets you run something within something else and return, it would be more useful.)
I don't see many sets of instructions that say to duplicate some code, compared to the number of places it says that you should inherit from class X to do something. Does the DAAB actually say "duplicate this" rather than "inherit from this"? At 09:50 AM 10/1/2004, Shawn Wildermuth wrote >Thanks Tom... > >Don't you love "Editor Inheritance"? > >Thanks, > >Shawn Wildermuth >Sr. Consultant >Magenic Technology >http://www.magenic.com >http://adoguy.com >C# MVP, Author and Speaker > >-----Original Message----- >From: On Behalf Of Thomas Tomiczek >Sent: Friday, October 01, 2004 9:39 AM >To: [EMAIL PROTECTED] >Subject: Re: [ADVANCED-DOTNET] sqlDataReader and syntax error in SQL statement > >Shawn, they are not worth it. >[snip] >Thomas Tomiczek >THONA Software & Consulting Ltd. >(Microsoft MVP C#/.NET) >(CTO PowerNodes Ltd.) >[snip] J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
