Simon Fell > Its just code > Interop is hard
Regardless of what anyone (Vendor's in particular) will tell you, getting real world interop is hard (i.e. across more than 2 toolkits), Nelson will talking about this at ETech. Dare argues that doing contract first with the tools is better than doing it by hand (i.e. write the WSDL/XSD by hand) because if you do it by hand you'll use constructs that the tools don't like. Well, if you use the tools, then all that means is that you'll use constructs that one particular tool is ok with, but you'll have no idea how many other tools will / won't like it. If you're trying to build a service with wide ranging interop (like Nelson & I am) then you're pretty much stuck with having to try every little change with every toolkit you remotely care about, you can read as many WS-I docs as you like, they won't tell you that you really want to avoid trying to send a nil xsd:int to .NET.