I am pretty sure ( eg slightly better than a guess) it does inherit serializable from DataTable .
Ben -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Green Sent: Sunday, 23 June 2002 6:59 AM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Strongly Typed DataTables aren't serializable - why? Hi Mitch, > The GetChanges() method doesn't actually serialize the DataSet > it clones it then does a bit of manual twiddling based on the > row states of the data. I guess you could grab the generated > code and make the necessary modifications yourself. Thanks, but I'm still interested in why strongly typed datatables aren't marked serializable in the first place. I'm also interested in the reason for the following curious behaviour... When I used GetChanges() on a strongly typed *datatable* and then tried to send that object across a remoting boundary I received a serialization error. When I used GetChanges() on the same datatable's strongly typed *dataset* I didn't receive a serialization error when sending the object across a remoting boundary. I'm assuming the strongly typed dataset uses custom serialization that effectively ignores the absence of the serialization attribute on its associated strongly typed datatables. Dan Green [ http://dotnetdan.com -- putting the dan in .net ] You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
