
Signature
Regards,
Phillip Johnson (MCSD For .NET)
PJ Software Development
www.pjsoftwaredevelopment.com
It is an easy offset. This time of year, it is 5 hours off. During the
summer, you move ahead one hour, which makes it four hours.
There are some methods on the DateTime structure you should look at:
ToLocalTime() - This is probably the most useful for you
http://msdn2.microsoft.com/en-us/library/system.datetime.tolocaltime.aspx
ToUniversalTime() - opposite direction
http://msdn2.microsoft.com/en-us/library/system.datetime.tolocaltime.aspx

Signature
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
*************************************************
> Hi,
>
[quoted text clipped - 13 lines]
> the site and change the time difference, but would prefer to have an
> automated solution.
Phil Johnson - 29 Jan 2008 19:32 GMT
Thanks George,
Looks ideal, I will give it a go.

Signature
Regards,
Phillip Johnson (MCSD For .NET)
PJ Software Development
www.pjsoftwaredevelopment.com
> It is an easy offset. This time of year, it is 5 hours off. During the
> summer, you move ahead one hour, which makes it four hours.
[quoted text clipped - 27 lines]
> > the site and change the time difference, but would prefer to have an
> > automated solution.
Phil Johnson - 04 Feb 2008 13:38 GMT
The link given above really got me started on the timezone conversion issue,
but I also had some hurdles to overcome when comparing javascript utc
datetime from the client to the .NET utc date time on the server.
Here is how I got around the issues....
http://pjsoftwaredeveloper.blogspot.com/2008/02/comparing-net-date-on-server-to-
clients.html

Signature
Regards,
Phillip Johnson (MCSD For .NET)
PJ Software Development
www.pjsoftwaredevelopment.com
> Thanks George,
>
[quoted text clipped - 31 lines]
> > > the site and change the time difference, but would prefer to have an
> > > automated solution.