Hi Param,

Welcome to MSDN newsgroup.
From your description, you're cosuming a certain webservice which will pass
DateTime object in your .NET client app. And you found that the default
serlized datetime output is not quite suit the webservice's actual
requirement, yes?

As for this quesiton, I think it is due to the current .net framework (1.0,
1.1)'s DateTime class's limitation. The current DateTime class is always
persisted as local time format (with TimeZone offset...), also the

2005-11-07T18:34:36.6990563-06:00

output you got is the default xml serlization output. Since we can not
control the underlying xmlserlization of the DateTime class( build-in basic
type), I'd suggest you consider modifying the .NET client proxy code,
change that class property which uesd to be DateTime type to a string type.
Then, we can use the DateTime class's ToString method to perform datetime
formatting which can output many different formats we want, here is the
related msdn reference on DateTime formatting:

#Standard DateTime Format Strings Output Examples
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconstandarddatetimefo
rmatstringsoutputexample.asp?frame=true

Also, another msdn article discussing on the best practice using DateTime
in .net 1.x application:

#Coding Best Practices Using DateTime in the .NET Framework
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/ht
ml/datetimecode.asp

Hope helps. Thanks,

Steven Cheng
Microsoft Online Support

--------------------

microsoft.public.dotnet.framework.aspnet.webservices:8304