Naughton FutilitiesNo RelationRoundtripping SoapDuration and TimeSpan- December 15, 2004 Clemens Vasters writes about XSD duration and its relationship with the .NET Timespan Type. Another quirk I have found with usage of these types is the fact that the conversion to the SoapDuration Type was not what I originally expected. It turns out that a Timespan that features a period of "about a year" highlights the issue. In fact, the conversion to SoapDuration assumes a year to contain 360 days (a month is considered to be 30 days). Therefore, a Timespan of 365 days yields.http://weblogs.asp.net/naughton/archive/2004/12/15/312730.aspx Detect Installed Version of WSE- December 9, 2004 I asked this question a few months ago but there have been two service packs since then.Can anyone recommend a reliable mechanism for the detection of WSE1WSE2being installed on a PCFor example, are there certain installed files andor registry settings thatexclusively indicate WSE2 Currently, I check the GAC for file versions. However, I'm not sure how to distinguish Service Packs (I don'tcan't have multiple Service Packs installed).I intend to implement the check in VBScript.Further, how..http://weblogs.asp.net/naughton/archive/2004/12/09/278835.aspx Access the XmlSerializer Temporary Assembly- December 8, 2004 I've been using the excellent XmlPreCompiler - GUI by Mathew Nolton, original idea by Chris Sells. My own idea was to extend the GUI to allow me to verify Types in a batch. For example, I sometimes want to check every Type in an Assembly. I have a basic implementation of that idea now. However, the side-effect of this feature is that, if run against an Assembly with hundreds of Types, I end up with literally thousands of files dumped in the "Documents and Settings" area on the hard disk; each...http://weblogs.asp.net/naughton/archive/2004/12/08/278230.aspx xsd:group Gets Lost In Translation- December 5, 2004 If an XML Schema contains an <xsd:group> definition, the contents of the <xsd:group> are embedded in the containing <xsd:complexType>. Reasonably, enough, the XSD.EXE tool mimics this behaviour, when generating a .NET class definition - <xsd:group> children become fields in the containing class. However, the fact that these fields originated in a reusable group is lost in the generated code. The developer working with just the generated classes must spot any reusability..http://weblogs.asp.net/naughton/archive/2004/12/05/275284.aspx |