Of course if you are using them.

Currently almost none is using standard data access methods in bigger projects. All the Data Access Layer (DAL) methods become very popular nowadays, just look at the most popular such as NHibernate, Sooda or the incoming ADO.NET. There is also an old friend among them, Typed DataSets which is better than many developers can imagine. Personally, I'm using it and I can't see any reason to switch to an another solution as this one works really fine and, apart some errors or some annoying features, gives a lot of good functionality. One of those good features is that the Typed DataSet is generated as a partial class and can be easily extend.

I my daily work I'm finding dozens of reasons for extending Typed DataSets at all levels, from adapters to rows and tables adding some logic, additional data control or so. There are two main reasons among all, why every generated adapter should be extended: transaction and timeout. Those two things are one of the most annoying lacks in the solution. By default, the Typed DataSet can't be executed inside of the transaction which is quite important issue in every more complicated project. Last time I found timeout as other annoying problem, as I had a few queries that needs a bit more than standard 40 seconds for execution. To bypass these two issues use simple code below:

Happy coding