I have another suggestion.

Store all event data using UTC, Greenwich time. So, instead of using System.DataTime.Now, use System.DateTime.UtcNow . At the database, instead of getdate(), use getutcDate().

This way, it is far easier to convert an event from time zone to timezone. Rather, than storing as (example) Pacific Time, then have to convert to Central time for a user preference (while "remembering" that it was stored as Pacific, its more direct. Also, if the database is moved to another server (in another timezone), it won't throw it off. Plus converting to zulu for vCal export is easy. Plus its easy to use the System.TimeZone class to convert back and forth, which automatically takes into account the daylight sayings start/end dates.

Alan,

I am now using your Calendar version 3.02.00.  The timezone portion is just what I was talking about.  Now when I export to Personal Calendar, the time is correct even though web server/database is in another time zone.

However, when a non-authenticated user is viewing my site (not logged in), all times are off.  So, a 7:00am UTC-700 (Mountain time) event is showing as 1:29pm. This is in 3 places:
1. the event list below the calendar. I guess thats the events for the selected day.

2. Week View

3. Calendar List module.

All when not logged in.   The Event "Detail" view of a single event is fine.  It seems the event detail uses the portal timezone when user timezone not available (i.e. not logged in).  This same technique should be be used all over.

Jeff.