Question: I recently switched my hosting provider and due to the time zone that the server is now in, my code has stopped working. 

The hosting server reports in Pacific time, However, my code needs to work with GMT as my site is for the UK market. So, all my displays and searches need to be in the format dd/MM/yyyy

How can I account for the difference? 

For instance, when I do a DateTime.Parse("03/11/2008") it fail as I assume the 'Parse' is against the servers settings. I also get "String was not recognized as a valid DateTime." throughout my code.

Answer: 
In order to avoid dealing with these very boring issues, I advise you to allways parse your data following the standard and unique SQL/ISO date format which is YYYY-MM-DD. Your queries will then work internationally, whatever are the date parameters on your main server or on the querying clients (where local date settings might be different than main server settings)!
I had this problem which the above answers didn't solve. So maybe this can help someone not to tear all their hair off..

I got NaN-NaN-Nan on the new server in my date-textbox. Found out that the new server had the internet explorer option "Display intranet sites in Compability Mode". 
Workaround here was to put 

```
<meta http-equiv="X-UA-Compatible" content="IE=9; IE=8; IE=7; IE=EDGE" / >

```

in the head of the aspx to force off compability mode.

This solved a lot of weird stuff that was going on.
Hope this helps someone!