Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Mar 20, 2006 07:11 PM|LINK
>>Could you mention what code generator currenly you are using?
I am using typed dataset in VS 2005.For every table 1000 lines of code is generated.
I put all the datasets in one namespace and use "table module" pattern from POEAA.(Martin Fowler)
I have threw out the stateful custom business objects.I use static methods to apply the business logic.
But typed dataset approach is cool if your database schema is isomorpic to your domain model and it is not complicated with many relations.I rationalized my domain to work with the typed dataset.
But looking after the code I see no reason to use a "data access layer".As I see it as an uncessary layer to encapsulate staff.(putting things under the rug)
Some might say I am really coupled with the RDBMS schema, but tell me who isn't.
Having a data access layer is like marrying someone and having a fair with another women.