Strongly-typed DataSet Article on

February 8, 2006

I have an article entitled Using Strongly-Typed Data Access in Visual Studio 2005 and ASP.NET 2.0 on the popular ASP.NET developer website For people who are new to strongly-typing their data access layer, it explores some of the features of strongly-typed DataSets in Visual Studio 2005. This is a good introductory article for people who don’t know what an O/R Mapper is and why it will save them time and effort.


3 Responses to “Strongly-typed DataSet Article on”

  1. Rachel Says:

    Thank you for writting this.
    I had been developing with for quite awhile the sloppy way until reading ExamCram MCAD 70-315 which uses strongly typed datasets which make trouble shooting much easier.
    Now I run around to everyone else’s desks when their ADO fails trying to get them to use strongly typed data sets, often to no avail!

  2. Bill Yeager Says:

    I’m a big fan of using STD’s. In VS.Net 2001 & 2003, I used them exclusively (using the component designer to generate a STD via a dataadpater).

    However, there is a problem using them in VS.Net 2005 if you don’t use the data access logic embedded in the STD designer generated code.

    If you have a separate data access tier and a separate middle tier (used with the ObjectDataSource), the UPDATE/DELETE/INSERT statements don’t work with an ObjectDataSource. The SELECT method works fine, but not the updates.

    If you use the data access logic within the generated STD, it’s fine. However, there are plenty of companies who want separation of dataaccess code from the middle-tier and Microsoft “blew it” here.

    Separating it out and executing a bottom tier dataaccess component from your middle tier object, is not working with the Updates (as long as you use an ObjectDataSource with it).

    I also agree with Rachel. Even though STD’s are the greatest thing since sliced bread, it’s amazing to me that hardly any companies use it or don’t even know what it is. I blame MS for that. Almost every book you pick up about dataaceess uses untyped datasets. Unfortunately, these people just can’t see the full benefits of STD’s even after showing them and explaining it to them.

    If you have an answer as to how you can get the ObjectDataSource to work with STD’s (using your own separate dataaccess layer – not the dataacess built into the STD which makes it a two tier app instead of a more flexible 3 tier app), I’m all ears…..

  3. Phil Says:

    Thanks for the post on 4 guys. What would be really interesting to those of us actually using the typed ds is an example where you use date from both a master and a detail table in the same gridview. Or better yet add a relater table to the mix. Now that would be valuable.

    I know there are plenty of people out there that need the doggy, piggy, bunny primer on a flat table but any kind of enterprise app will not have a data structure that simple.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: