Re: DataSet and best practice in 2.0

Tech-Archive recommends: Fix windows errors by optimizing your registry

thanks for the reply.
i am indeed moving data across machine boundaries in a single
application. using dataset with different platforms wouldn't make much
sense.

as far as switching to binary serialization, that would mean switching
from webservices to remoting no ? that is a significant change. i was
wondering about datasets in webservices, and if it is worth creating
strongly typed collections for every purpose instead of using datasets.


Well, if you are truly moving data "across app boundaries" then you should
follow best practices for SOA and use contract-first, interoperable web
services. The problem with DataSets in that scenario is that the WSDL that
they generate is not specific clean enough to allow non-.NET clients to
meaningfully work with the data.

If you are just moving data across machine boundaries within a single
applciation, then I wouldn't worry about the performance hit too much. If
it becomes an issue you can later move to binary serialization without too
much disruption. This is an important differece from 1.1, where you had to
make a performance-related decision about using DataSets during the initial
application design, when you often have no idea whether the performance of
XML-Serialization will be an issue.

David

.