Contract-first web services
I just received an e-mail from my fellow RD Christian Weyer, an excerpt:
There has been a lot of buzz around schema-based contract-first Web services design & development lately (as opposed to code-based contract-first with juggling all the XML-related .NET attributes). Nearly everybody thinks that it is a good thing, and that we finally should reach a state where we all can live and breath it. But most people have been complaining about the lack of tool support for the so called 'first step'. We have two big steps
involved:
* Design your contract's messages and interface
* Generate code from the contract
Our WSCF (aka WsContractFirst) tool has been quite good at the last one of the two points: code generation. But there always was a missing link to how to design and model the contract effectively.
Now we from thinktecture are proud to present the next version of our very successful and freely available WSCF. This new version 0.4 now offers a simple yet powerful WSDL Wizard that abstracts away all the nitty-gritty details of WSDL and therefore does not give room for making errors and wrong assumptions just by trying to use and applying everything that can be done stated by the original WSDL specification. Just model your data and messages in XSD files and off you go.
Interested? Go here and dowload the tool.