Caliburn.Micro is an MVVM framework that aims to simplify building WPF, Silverlight, and Windows Phone applications using common UI patterns like MVVM. It provides features like automatic view-viewmodel resolution through conventions, an event aggregator for loose coupling between components, window management, and coroutines for asynchronous programming. The framework handles common tasks like UI lifecycle management and removes much of the boilerplate code associated with building MVVM applications.

1. Caliburn.Micro Solving real word problems implementing MVVM bart.wullems@ordina.be http://bartwullems.blogspot.com

2. Agenda MVVM Frameworks Caliburn(.Micro) What is it? Patterns Features

3. MVVM Frameworks

4. MVVM Frameworks Explorer Source: http://www.japf.fr/silverlight/mvvm/index.html/

5. What is Caliburn?

6. 6

7. What is Caliburn? “Caliburn is a set of libraries designed to aid in the development of WPF, Silverlight and WP7 applications” http://caliburnmicro.codeplex.com

8. Fact Implementing a User Interface is easy

9. Fact Implementing a maintainable User Interface is hard

10. Goals of Caliburn Build WPF/SL/WP7 Applications in a TDD friendly way Simplify usage of various UI design patterns in WPF/SL/WP7 Simplify common UI tasks Provide solutions to common UI architecture problems Remove the boilerplate code when building MVVM app’s

11. It’s all about patterns...

12. Presentation Model Presentation Model coordinates changes in the Model Presentation Model View calls operations View Model Operations Data Model alerts the Presentation Model View synchronizes with PresentationModel

13. Model – View – ViewModel Change notification Presenter coordinates changes in the Model ViewModel View Model Commands Data View binds to commands and data Model alerts the Controller

14. Command ICommand Invoker + Execute() + CanExecute() Command Receiver

15. Application Controller “A centralized point for handling screen navigation and the flow of an application.” – Martin Fowler

16. Service Locator Service A Class A Locator Service B

17. Dependency Injection Container Dependency Injection Container Component

18. Event Aggregator Results Model Criteria Model hub Publish Handle Publish Handle Advert Model Recent Searches Model

19. The application

20. The Application

21. The Application No Code Behind No Event Wireups No Commands No Data Binding No Data Templates No Async Programming No Custom Controls No 3rd Party Libraries

22. Features

23. Features Overview Basic configuration and bootstrapping Actions Screens, Conductors and Composition All about conventions The Window Manager The Event Aggregator Coroutines

24. Basic Configuration Convention over Configuration Limited amount of configuration needed Simple naming convention to locate Views for ViewModels. e.g. MyApp.ViewModels.MyViewModelMyApp.Views.MyView. Bootstrapper Should run at startup Specifies the root view model(=Application Shell) View Model First but can be changed IoC Has it’s own small IoC container Can be replaced by the IoC of your choice(MEF, Unity,…)

25. Demo- Basic Configuration

26. Actions - Basics Command implementation for Caliburn.Micro Extend databinding to bind not only data but also methods Leverages System.Windows.Interactivity for it’s trigger mechanism. Use anything that inherits from TriggerBaseto trigger the sending of an action message(events, …) No need to add a command class and/or property on VM Allows: Execution of methods Passing data from the UI into methods Synchronous/Asynchronous calls

27. Action - Guards Guard property Handler: “SayHello” message Guard property: “CanSayHello” CM will observe changes in that property and re-evaluate the guard accordingly. Based on INotifyPropertyChanged to refresh trigger availability Can change the state of the bound control E.g. change a button to disabled, hide a menu item,…

28. Demo- Actions

29. UI Lifecycle Management Often using MVVM involves tricky UI lifecycle issues for various UI components Activation Deactivation Shutdown Caliburn.Micro handles this lifecycle with Screens, Conductors and Screen Collections 29

30. UI Lifecycle Management Screen A statefulunit of work existing within the presentation tier of an application. Has a lifecycle associated with it. Screen Conductor Enforces the Screen Activation Lifecycle Activates screens. Deactivates screens. Allows graceful shutdown. Screen Collection Maintains the list of currently opened screens or documents

31. UI Lifecycle Management Conductor Screen 1 Screen 2 Active Active Activate() Screen 2 Deactive() Screen 1 CanClose() Returns True Activate() Screen 2

32. Demo- Simple Navigation

33. Demo- Simple MDI

34. Conventions Removes the need to write boiler plate code Fully customizable Can be turned off if you hate them On by default Conventions for View/ViewModel resolution Data binding Action binding

35. Demo- Conventions

36. Window Manager Provides a View-Model-centric way of displaying Windows (ChildWindow in SL and Window in WPF). Available methods ShowDialog ShowWindow ShowPopup Uses a Conductor under the hood

37. Demo – Window Manager

38. Event Aggregator Communicate between objects in a loosely coupled way Follows a bus-style pub/sub model. Uses weak references Publishes on the UI thread.

39. Demo – Event Aggregator

40. Coroutines Wikipedia: “In computer science, coroutines are program components that generalize subroutines to allow multiple entry points for suspending and resuming execution at certain locations. Coroutines are well-suited for implementing more familiar program components such as cooperative tasks, iterators, infinite lists and pipes.”

41. Coroutines Introduces asynchronous programming in a simple way. Build on top of iterators. 2 required actions Implement the IResult interface on some class, representing the task you wish to execute Yield instances of IResult from an Action

42. Coroutines Allows you to execute a method, pause it’s execution, do something else, come back and resume execution where you left off. Extremely powerful in task-based programming

43. Coroutines Silverlight example: Dynamically download and show screens not part of the main package.

44. Coroutines Show “Loading” indicator Load Screen() yieldreturn yieldreturn yieldreturn yieldreturn Asynchronously download the external package Hide“Loading” indicator Navigate to a particular screen inside the dynamic module

45. Demo - Coroutines

46. TODAY’s TALK Remember! Still a lot to discover... CALIBURN

47. Conclusions Caliburn.Micro is clean and simple Allows you to create very rich applications with a strong focus on maintainability and reuse A LOT of UI principles are applied in Caliburn.Micro Also check it’s big brother Caliburn “If you don’t like the code, use it as a learning tool” 47