Those who have followed Caliburn over the past 6-8 months have probably heard alot about Caliburn.Micro as well. Whenever somebody has tweeted about getting started with Caliburn, Rob Eisenberg has quickly guided them to Caliburn.Micro. You don't need to be a rocket scientist to figure out that he has his reasons!
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
For the last two days we have been struggling with a rather peculiar problem in a Caliburn solution. In a ResourceDictionary we had defined a Popup with a ListBox containing some textblocks and buttons. The buttons are bound to a Presenter (Caliburn v1.1), and we tried to pass a parameter with the Message.
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:
With a little tweaking on Google Analytics, I managed to come up with a map overlay of all page view related to Caliburn:
In this post I will look into the unit testing features of Caliburn and try to give a quick introduction to the essentials of what you need to know to write a couple of small unit tests in NUnit. The documentations on caliburn.codeplex.com on unit testing is fairly good, so I will only try to fill in some missing pieces and give a quick start guide to unit testing Caliburn. If or when you bump into problems with the simple setup described here, it's time to move over to more detailed documentation available in both the documentation and discussion forum on Codeplex.