In my speech I tried to sum up some of the advantages of using a robust framwork when doing developing in Silverlight or WPF, framworks like: MVVM Light, Caliburn or Caliburn.Micro.
The source code from my speech can be found at filehub.iserialized.com. The example is a fairly simple WPF application, and the GUI it selves sucks, as my focus has been:
- Core Caliburn functionality
- The simplicity of using IoC in the combination WPF and Caliburn
This last week I have looked into more details on how to upgrade a Caliburn v1 project to Caliburn v2. Marco Amendola wrote a very nice post on this back in January 2010, but the Caliburn naming conventions have change a bit since then, and as seen from the checkin-ins, but hopefully not too many "Don't hate me updates" from now as Rob Eisenberg describes them
When I first dived into the upgrade, @EisenbergEffect tweeted me a short list of major/most essential changes in namings: