Do you want to write yourself XSD/WSDL/Policy contracts?
Clemens and Aaron argue about the way a developer should share the service contract. But Aaron is wrong. I know that it is essential today to work out the contract on that level (XSD/WSDL/Policy). Most developers just wish to have tools that abstract that level from them. Clemens is absolutely right that the majority of developers have not the desire to work on the angle bracket level. What a wonderful world would it be if a developer could just define the contract on a tool level without the details about XSD/WSDL/Profile. Of course, today they have to know those, as tools are not that powerful and handcrafting is sometimes necessary. Yesterday I had a workshop about WSE 2.0 with a customer and as they saw the policy configuration file the WSE Wizard generated they just said: We hope that we never have to touch this file. Aaron compared this to the COM days. I wouldn’t do this comparison at all as VB developers never had the chance to influence the IDL. You often wrote your IDL by hand and compiled it to use it as binary reference in your VB project. But this was just because VB had no tooling to influence IDL generation. It was just a standard behavior and therefore not the fault of the developer, it was the fault of the tool. And hopefully we will have tools in the future where we don’t have to think about WSDL or even Profile. But in the meantime we are doomed to know what is in there.