Let me be clear, I am *still* and advocate of DataSets (though Typed DataSets in .NET 2.0 are snarky to say the least). The story isn't that DataSets over WebServices are bad, but that Web Services should be a message oriented design...not a remote object design IMHO. If your DataSets reflect the message of the web service, then passing them over Web Services works. The problem comes in with the serialization format of the DataSets. In general I've suggested that users pass DataSets as pure XML (not the serialized format) in one of two ways depending on the performance requirements:
return new XmlDataDocument(yourDataSet); - or - XmlDocument doc = new XmlDocument(); doc.Load(yourDataSet.GetXml()); return doc; Thanks, Shawn Wildermuth Wildermuth Consulting Services, LLC http://adoguy.com C# MVP, MCSD.NET, Author and Speaker > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Chris Wuestefeld > Sent: Wednesday, October 11, 2006 9:59 AM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Web services, DataSets and > making use of XSDs... > > Don: > > DATASETS over Web Service = Very Bad > > Shawn: > > Don is EXACTLY correct > > Since this is the architecture of one of our most important > apps (and it's working quite well), I'm interested in the > reasoning behind this. Does anyone have pointers to articles? > > =================================== > This list is hosted by DevelopMentor. http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
