I built my first Indigo service in the hands-on labs. I got totally sidetracked by some new things I noticed about how Indigo does WSDL generation...

• WSDL.EXE is replaced by WSDLGEN.exe in the Longhorn SDK
• There's a whole set of message-oriented types to control serialization, like System.MessageBus.TypedMessage, [MessageAttribute] and [MessageBodyAttribute].
• When WSDLGEN.exe generates schemas for these types, it looks like it does so by generating named elements at the global scope, not by generating actual XSD types. I need to confirm this with some more experimentation, but it looks like Tim Ewalds views on schema have propagated :)
• Type schemas look like they are generated into separated XSD files that are then imported into the WSDL file. Score one for Yasser and the WSDL-first folks!