Monday, October 04, 2004

DateTime Serialization Part 2 

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

About the Author

You may be wondering who I am (or may not!), but I've been in the industry 16+ years working on a variety of systems from IBM mainframes as a CICS systems programmer, to developing on Unix and Windows based systems. At the moment, I'm currently working for a Microsoft Gold Partner in the UK called Solidsoft who specialise in systems integration using BizTalk Server. My position is generally dictated by what I'm doing, but normally as a solutions architect/consultant helping clients with their integration projects involving, yes you guessed it: BizTalk Server.

Disclaimer: all the views expressed here are my own and do not necessarily represent the views of Solidsoft Ltd or indeed any other company.