Viewmodel Active Awareness In A Prism Based Application
Yesterday, while chatting with the talented Jeremiah Morrill and other WPF Disciples about some MVVM subtleties (for the full post see here), Jeremiah briefly touched on the topic of providing ViewModels with the awareness of being active or inactive within a Prism based application. I wanted to explore this further, and decided to integrate this functionality into Calcium. What I provide here isn’t rocket science, and merely serves to illustrate one of indeed many design...
Synchronous Invocation Of Delegates With The Silverlight Dispatcher
Introduction In this post I would like to briefly discuss the System.Windows.Threading.Dispatcher class, and the significant differences between its Silverlight and Desktop CLR implementations. We are going to look at solving two things: Consuming the UI’s Dispatcher in Silverlight before a page has been instanciated. Allowing for synchronous invocation of delegates on the UI thread. Background Recently my good friend Sacha Barber published an article, and in the comments of which we briefly touched on...
Clog Project Source Integrated Into Calcium
I am pleased to announce that the Clog project has been integrated into Calcium. The source code for both the Silverlight and Desktop CLR Clog projects is now located along with the Calcium source code on Codeplex. Why did I take this step? The reason is that there are shared projects across Clog and Calcium, and maintaining two codebases would not be a good thing. One of my goals when publishing software is to make...
Alt.net Swiss Group
Last night I had the pleasure of speaking at the ALT.NET Swiss group in Geneva.
I spoke on composite applications, Prism, Calcium, and T4 Generated Metadata.
Valeriu Caraulean spoke on MVVM, BLToolkit and Caliburn.
Thanks to Frederic Schafer for organising the event, and to Atif Aziz and Cargill International SA for the location.
Catch us at the next meeting!
Using T4 To Generate Pack Uris For Xaml Files
Yesterday my fellow WPF Disciple Paul Stovell got me thinking about resolving XAML file paths. As Paul points out, there doesn’t appear to be an easy way to locate the URI for a XAML file. Internally, the generated .g.cs makes use of the path, as shown in the following excerpt: public void InitializeComponent() { if (_contentLoaded) { return; } _contentLoaded = true; System.Uri resourceLocater = new System.Uri("/PageCollection;component/pages/page1.xaml", System.UriKind.Relative); #line 1 "..\..\..\Pages\Page1.xaml" System.Windows.Application.LoadComponent(this, resourceLocater); #line default...