My situation is a need to take a dataset that contains table with a DateTime column, and have that whole dataset sent as a parameter or a return value of a remoting operation, but have the DateTime column sent as xs:date instead of xs:dateTime
The reason for this is cross-timezone datetime storage -- a person using client software on the East Coast enters a date, which gets saved to the row as, say, 02-26-2004 00:00:00. However, the server is on the West Coast, and the date gets deserialized as 02-25-2004 21:00:00, and gets stored in the database as such. Needing to store only the _date_ part of this value, it would seem that the natural thing to do would be to have the original serialization use xs:date instead of xs:dateTime. However, I can't find a way to force a datacolumn to use a different-than-default serialization for its value. Perhaps someone can suggest a way to solve this other than waiting for .NET 2.0 which supposedly somehow fixes this? Thanks in advance, -ilya haykinson kareo =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
