.NET Zone is brought to you in partnership with:

I’ve been a Windows developer since 3.0 and caught the Visual Basic wave early with v1. I’ve released a “production” application in every version of VB since then (except VB for DOS). Focusing on enterprise, line-of-business development I’ve built Call Center Applications, Mortgage finance systems, Customer Relationship Management tools and more recently I’ve been in the Litigation Support/Electronic Data Discovery/Electronically Stored Information space. Greg is a DZone MVB and is not an employee of DZone and has posted 477 posts at DZone. You can read more from them at their website. View Full User Profile

Composing Maintainable XAML Apps - Two Hour Video Workshop

  • submit to reddit

UserGroup.tv - Composing maintainable apps in XAML


Michael Perry


Of all the user interface technologies that have reached the main stream, from HTML to Windows Forms to Java Swing, XAML is the most composable. It offers an incredible degree of code reuse, customization, and componentization. It has so many options for piecing interfaces together, that selecting the right one can sometimes be overwhelming.

This February at Dallas XAML, we will dive deep into several composition patterns. These include:

  • User controls
  • Data templates
  • Control templates
  • Content presenters

Bring your laptop and code along. The workshop will include several checkpoints to ensure you stay caught up.

Choose the right pattern, and your WPF, Silverlight, Phone, or Metro code will be well organized and easy to maintain. Your co-workers will buy you lunch, and your apps will bring in tons of cash.


My name is Greg, and I don't "compose" my XAML App's well. Now I break up my backend pretty well, domain objects, libraries and stuff are all highly reusable, but my UI? Um... not so much... Must remember that doing it right upfront, while maybe a little longer, will almost always pay off in the end.

Published at DZone with permission of Greg Duncan, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)