>Now to find the software equivalent. AN uninitialised variable? Well, there's no code involved, so I'm now carefully comparing the environments. I notice that SDK 6.1, 7.0A and 7.1 are on my dev machine. The other machine only has 7.0A. Suspicious I think, as each contains xsd.exe which is responsible for generating XSD tool code. So I run the following test to see if the output files differ:
@echo off "C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin\xsd.exe" ColsDS.xsd /d /o:v61 /eld "C:\Program Files\Microsoft SDKs\Windows\v7.0A\Bin\xsd.exe" ColsDS.xsd /d /o:v70A /eld "C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\xsd.exe" ColsDS.xsd /d /o:v71 /eld They differ only by a version comment line. So it's not a problem with a particular version of xsd.exe., It may be the way the VS2010 is calling xsd.exe, possibly internally omitting the vital /eld switch to generate generic classes. The relationship between different versions of Visual Studio and the SDKs is rather muddy. Searching continues... Greg
