Publishing changes to a service API can be a bit tricky, at least for your clients. In this video excerpt from Aaron Skonnard and Scott Seely’s course WCF for Architects Scott explains some of the “Do’s and Don’ts” for data versioning and how to minimize the pain on your clients when you release new services. In the complete course the duo cover other key topics such as REST services, SOAP, and serialization.
Aaron is a co-founder of Pluralsight where he serves as the Chief Executive Officer.
He has presented at many popular developer conferences like PDC, TechEd, and VSLive! Microsoft recognized Aaron as an MVP in the “Connected Systems” developer community for eight years. Aaron has written numerous books, articles, and whitepapers including the Essential XML Quick Reference (Addison Wesley, 2001), Essential XML (Addison Wesley, 2000), and his popular columns in MSDN Magazine.
Scott Seely is a Microsoft Regional Director and Microsoft MVP. From 2002 to 2006, Scott was a developer on the WCF/Indigo team at Microsoft. Scott has been writing about SOAP and REST Web Services since 2000. He has authored and co-authored five books and dozens of articles on the topic.
If you’d like to learn more about WCF from the Architect’s point of view, this course is for you.
You can watch the full HD version of this video along with the other 4 hrs 3 min of video found in this professional course by subscribing to Pluralsight. Visit WCF for Architects to view the full course outline. Pluralsight subscribers also benefit from cool features like mobile apps, full library search, progress tracking, exercise files, assessments, and offline viewing. Happy learning!
Pingback: Revisiting REST Versioning « Karmic Code Monkey