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!
Today I came across the following error opening a WPF XAML file in Visual Studio:
There is no editor available for 'xxx'. Make sure the application for the file type (.xaml) is installed
You could get the same kind of error for aspx:
There is no editor available for 'xxx'. Make sure the application for the file type (.asxp) is installed
I tried upgrading to Service Pack 1 of Visual Studio, but it didn't help at all! For some strange reason there seems to be some VSPacakges that suddenly got a SkipLoading tag. You can easily solve this through the Visual Studio command prompt by typing:
This clears all SkipLoading tags added to VSPackages, normally added by users wanting to avoid loading problem VSPackages.
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.
In this blog post I will look into the AutoCompleteBox in the WPF Toolkit, added in the february release of the WPF Toolkit. The AutoCompleteBox works, just the way I had expected it, but it actually adds a couple of more features than what I would have expected. Only one dll is needed to use the AutoCompleteBox:
I will not describe all the features in details, only describe the basics of what you need to know to use it! To add a basic AutoCompleteBox, I just add the following line to my XAML:
<Controls:AutoCompleteBox Name="autocompleteBox" />
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.