Be there or be seriously square. We're at DevCon5 - The Applied XML Developer's Conference! (That's DevCon, not DEFCON :) )
It's only $345 for 2 full days of sessions! It'll be at Skamania this year which is about 40 mins from PDX. The conference is 20-Oct and 21-Oct.
The list of folks speaking is crazy. Tim Bray (co-inventor of XML), Don Box, Tim Ewald, Ted Neward, Jeff Barr from Amazon.com, Doug Purdy (XmlSerialization), and many more.
Sneaking into this list of literati are the humble Patrick Cauldwell and myself (this is his second time speaking at a DevCon, this is my first) giving a session on the first day of the 'Con.
We'll be talking about the Corillian project that we've been working on for the last year or so. Corillian, the company we work for, enables folks to bank via the web. Roughly 25% of the people in the U.S. who bank online are using Corillian software. It's all Microsoft, lots of XML, and lately, lots of .NET and XML.
Bringing Strongly Typed Business Objects to Legacy Financial Systems with XML SchemaPatrick Cauldwell and Scott HanselmanOften a development team wont pay attention to a Word Document, but a compiler error will get their attention. By extending XSD and WSDL with custom attributes and custom code generation, we can enforce contracts between development teams to reduce development time. XSD.EXE maps a declarative syntax one-to-one to a programmatic instance of the same thing. However, if your business requirements can be captured in a schema document and annotated, why not generated as many source artifacts as you can?
Bringing Strongly Typed Business Objects to Legacy Financial Systems with XML Schema
Patrick Cauldwell and Scott Hanselman
Often a development team wont pay attention to a Word Document, but a compiler error will get their attention. By extending XSD and WSDL with custom attributes and custom code generation, we can enforce contracts between development teams to reduce development time. XSD.EXE maps a declarative syntax one-to-one to a programmatic instance of the same thing. However, if your business requirements can be captured in a schema document and annotated, why not generated as many source artifacts as you can?
Ads by The Lounge