Caliburn Posts



1-5 of 6

WPF Application with Caliburn - Part Two (Friday, January 15, 2010)

In this part of the tutorial, we'll enhance our shell view to display other presenters and add Save and Print support for presenters supporting it. You can use generalize this example and learn how to implement generic features in your shell.

 


WPF Application with Caliburn - Part One (Wednesday, December 30, 2009)

Back in May 2008, I did two posts on how to implement a composite application using Caliburn framework. By that time, Caliburn was still in pre-alpha stage. With lots of the changes along the way to reach Release Candidate, those content are not valid anymore, so I thought a new post to show how you can use Caliburn to build a WPF application is in order. 


Caliburn = Less Code? (Wednesday, September 02, 2009)

Caliburn is an application framework for WPF / Silverlight. If you're developing applications for these platforms, there are many reasons why you definitely need to be using this framework, but today, I noticed how using this framework resulted writing less code while doing more. Let's see how writing a small WPF application using MVVM pattern is different when using Caliburn


Caliburn or Prism (Saturday, July 19, 2008)

I was using Caliburn framework on a pet project of mine for the last couple of weeks. At some point of time, when I merged my custom made styles, application did not open views anymore, complaining something is wrong with my styles. I spent a lot of time to figure out what is wrong, but found nothing, except if I do NOT use custom styles everything is working fine (Maybe that IS a proof of my styles having some error!).So, I decided to port the application to Prism (now called Composite WPF). How smooth was the port procedure, you might 


WPF Composite Application with Caliburn - Part Two (Thursday, June 05, 2008)

In the first part, we learned how to create a basic composite UI with Cliburn Framework. In this part we'll see how Presenters play their part and how we do binding, etc.Views and PresentersBefore start working with our Presenters and Views, we need to introduce them to Caliburn. We could do this in IoC container configuration file, or via code (that's what we do here). As for Windsor, we need to create a Facility which is automatically loaded when the assembliy gets loaded, and their Init method is called, so providing type information for our Views as well as our