Using Strongly Typed Objects and Collections to replace DataSet’s in your .NET applications

I've put the first four articles on the subject of using Drtongly Strongly typed objects to represent your business Data on to my blog, they are as follows: -

Part 1: Reasons for the Switch

http://weblogs.asp.net/plip/articles/111121.aspx

Part 2: The Strongly Typed Object

http://weblogs.asp.net/plip/articles/111125.aspx

Part 3: Populating Objects and Collections from Databases

http://weblogs.asp.net/plip/articles/111126.aspx

Part 4: Sorting and Filtering Strongly Typed Collections

http://weblogs.asp.net/plip/articles/111127.aspx

As ever, if you have any questions, queries or suggestions please don't hesitate to get in touch either via the contact form or directly to phil@winstanley.name

Published Sunday, April 11, 2004 9:26 AM by Plip
Filed under:

Comments

# re: Using Strongly Typed Objects and Collections to replace DataSet’s in your .NET applications

Tuesday, April 13, 2004 8:40 AM by Alexandre Rocco
Good info on these!

Just a typo on this page. On "Drtongly", i think you meant Strongly

But it's very good info overall!
Tks for sharing

--Alexandre

# re: Using Strongly Typed Objects and Collections to replace DataSet’s in your .NET applications

Tuesday, April 13, 2004 9:01 AM by Phil Winstanley
Thanks for the note of appreciation! The Spelling has been Fixed now ;) Gawd I need to read things before clicking "SAVE".

# re: Building Strongly Typed Nested Collections Part 3

Wednesday, April 14, 2004 2:23 AM by TrackBack

# re: Using Strongly Typed Objects and Collections to replace DataSet’s in your .NET applications

Monday, July 24, 2006 9:24 PM by Thomas Miller

This is a great debate. I really enjoy reading about these techniques. In the end, each architecture has its own pros and cons. A good architect will know how to make a decision on it.

I will explain how I make the decision to use Datasets vs. Custom Entities

When to use datasets:

use when it is a database driven application. Period =]

When to use custom entities:

use when it is NOT a database driven application. For example, user controls like Infragistics, network applicactions like xCeed FTP, any software that will be resold or reused by others external to your organization.

p.s. Somebody who is a guru of sql is more valuable then somebody who is a guru of c#.

p.s.s. nobody will ever convince me that custom entities are faster than well written optimized sql queries!

Leave a Comment

(required) 
(required) 
(optional)
(required)