This project is read-only.

ObjectDataSource best practices?

Topics: Developer Forum, Project Management Forum, User Forum
Jul 17, 2007 at 2:11 AM
Edited Jan 26, 2008 at 9:05 PM
I bought the book and I think it's great! It allows me to see what professional development looks like in a full fledged project.

I have bought supplement books to help me along and I'm stuck on how the ObjectDataSource was used in this project.

The books I have been reading have rules for the use of a ObjectDataSouce. To the untrained eye, these rules seem to be ignored in this project. e.g.

An Data Class for an ObjectDataSource must...

Be stateless ( I don't think this rule was broken)
default no arg constructor ( false of The BeerHouse project)
All logic must be contained in one class( true of The BeerHouse project)
None of the linked methods (for selecting or updating records can be static ( false of The BeerHouse project)

I have read there were work-arounds using events from the ObjectDataSource but none were used in the BeerHouseProject.

My question is what am I missing? It appears that this project just ignores those rules and gets away with it gracefully.


It finally dawned on my what I was missing. The example in the book is right on. I love it.
Tim(almost novice) :-)