This document is an attempt to establish a common baseline for XAML and WPF developers. The guidelines provided here share the following goals:
These guidelines are the result of several years of development experience with XAML and WPF. In those years, a number of pitfalls have been encountered and, sometimes, circumvented. Some of the guidelines in this document try to make sure that you do not stumble into the same pitfalls. The work was informed by many contributors, both inside and outside of Philips Healthcare. You can find their names in the Acknowledgements section.
These guidelines are a living and evolving document. While we continue to use XAML and WPF, and may even start using WPF 4.5 in the future, we will gain additional knowledge and experience that will lead to better insights and updates of this document.
The presentation of the guidelines is derived from the Framework Design Guidelines book by Cwalina and Abrams. Each guideline is presented as a recommendation using Do, Consider, Avoid, and Do not.
Most guidelines are illustrated with examples or practices, with a good practice indicated by a ✔ and a bad practice by a ✘.
The writing of these coding guidelines would not have been possible without the hard work and valuable insights of the following individuals. The contributors are listed in alphabetical order. Many of the good suggestions in this document are theirs. As the author, the responsibility for the bad ones lies solely with me.
Lukasz Berek, Rob van Daal, Jack Geraats, Wilco Furster, Marija Grueva, Eric Heesakkers, Rob van Manen, Teun van de Merwe, Antoinette van Oeffel, Harold Peeters, Stephan Redering, and Joost van Rooijen.
The coding standard document consists of a set of rules. Rules are grouped together logically into so called categories. Each chapter deals with one category. A rule description contains the following items: