Monday, October 04, 2004
A colleague has just suggested that it may be because the BizTalk NT Service account may not have a profile, therefore no timezone information. So, setting a promoted property in Orchestration with the value DateTime.Now would potentially produce a time based on GMT with no timezone or daylight savings offsets in effect.
A mightily sound theory, but I haven't been able to try it yet.
Will post here when I've had a chance to do it and prove the theory once and for all...
Duncan's blog post on the subject can be found here