This project has moved and is read-only. For the latest updates, please go here.

Synchronize across time zones question

Apr 25, 2012 at 7:19 PM

Is there a way to set the start time so that 'Synchronize across time zones' check box is not checked when creating new trigger? I want to create a weekly trigger that starts a process every day at 7:00pm local time (central time). I created weekly trigger and set Trigger.StartBoundary to 7pm local time. Prior to DST change, it was working correctly and starting process at 7pm local time. After DST change, it's firing up the process 1hour later (8pm local time). I suspect it's due to 'Synchronize across time zones' check box. If there is no way to change 'Synchronize across time zones' check box through code, should I be using UTC time for Trigger.StartBoundary? Would that take care of the DST problem?

Thanks in advance!

Apr 25, 2012 at 11:05 PM

Checking the "Synchronize..." check box will force an "Unspecified" DateTime value to a UTC value. If the DateTime value is either "Local" or "UTC", then it should be checked already. Setting the StartBoundary to a DateTime with Kind = "Unspecified" will leave the checkbox unchecked.

I am not aware of anything in the library that specifically handles DST. I would try using UTC and see. Unfortunately, this is something handled by the native library and this wrapper has no control over that.

Apr 27, 2012 at 2:07 PM

Thanks for the reply. I tried using UTC time and noticed something interesting when I try to export a task. If I use UTC, the StartBoundary in XML file when I manually export the task is in the format '<date><utc time>Z'. If I use local time, then it's in the format of '<date><local time>+-<utc offset>'. It seems like the <utc offset> can be different based on whether the local time zone is in DST or not. I think that's what causing the start time of the task to be off by 1hour. Using UTC should work better I think.