Learning Silverlight

While I was taking the beta .NET 4 certification exams, I noticed a change. The Windows developer exam focused heavily on WPF and XAML (technologies I had decided to not learn). Needless to say, I failed that exam.

Fast forward a few months and I found an opportunity to work on a Silverlight application. I downloaded a demo twitter application to get started and learn the basics of what you can and can’t do in Silverlight. This was good and I started adding features. Of course, before long I found myself furiously refactoring and trying to identify some best practices to separate concerns and introduce some testing to make those refactorings easier. I’m starting to learn the MVVM pattern in Silverlight and will have a followup post on that, but for now, I’m just making sure that my code falls into one of those three categories

  1. Model
  2. View
  3. ViewModel
I am using the Telerik Silverlight controls to speed up development of new features. For unit and integration testing, I’m using the Silverlight unit test project types in the Silverlight Toolkit. This technology stack is easy to use for a single developer, but if I plan to offer the source code to my coworkers, there are a few additional steps that I would want to take including
  1. Isolating the Telerik controls as not everyone has access to the toolkit
  2. Implementing a unit testing framework that doesn’t run inside Visual Studio for continuous integration

Leave a Reply

Name *
Email *
Website