Pros and Cons of the Typed DataSet
The typed DataSet inherits from the untyped DataSet, so the pros and cons are largely the same. The typed DataSet also has these benefits:
Type-safe operations, with all their advantages
Data validationfor example, setup at design time
Data binding at design time
These disadvantages are associated with typed DataSets:
It has higher overhead than that of an untyped DataSet.
It's not exactly what you want in many situations. (Nothing concrete, just a feeling I get when I work with a typed DataSet.)
Those of you who have read Martin Fowler's Patterns of Enterprise Application Architecture (Addison-Wesley, 2002) will recognize that the patterns typically used when working with DataSets are the Table Module pattern and the Transaction Script pattern.