>>Wow, that sounds like a lot of unnecessary work! You can sub-class Typed DataSets to add functionality to them and still pass around those DataSets instead of BizObjects. I dunno ... maybe it's six of one, half dozen of the other. <g>
>>
>
>Those are the two schools of thought that I've seen for business objects on the .NET world. Some people build their business objects around datasets (kind of decorated datasets) while some other people build business objects that implement the ISomething interface (I forget the name)

I think if you are using business objects you should not be passing around DataSets - you should be shipping around the business object with teh data attached to it somehow. Otherwise you have to do things like reassign the DataSet to another object and that is fairly unclean at best. As it is you already must do that for Web Services and it causes all sorts of messy code to reattach everything again to a business object on the other end again.