I have recently begun planning a new project, and I needed to do all the standard pre-project decision making on build runners, test frameworks, continuous integration tool, IoC , and since it was going to need a UI, an MVVM framework. These decisions are usually quite quick since I tend to reuse the same things I used for my last project. However, every so often I take the time to evaluate the field of choices. ...
I just released an update for Caliburn.Micro.Logging , Caliburn.Micro.Logging.NLog, and Caliburn.Micro.Logging.log4net. All three are now at version 1.2.1, and are available on NuGet. This is a just a minor patch release with the version notes below. Please see the following posts for usage: Introducing Caliburn.Micro.Logging Introducing Caliburn.Micro.Logging.NLog Introducing Caliburn.Micro.Logging.log4net Version Notes Upgraded .NET 4 and Silverlight 4 versions to Caliburn.Micro 1.2.0 Created a psake build script to be used in Continuous Integration Moved samples into their own solution
I just released Caliburn.Micro.Autofac 1.2.1 to NuGet . This is a minor patch release, call it the OOPS release if you will. My build script was not good enough yet. It should be fixed now. Please see Introducing Caliburn.Micro.Autofac for usage. Version Notes Fixed missing references in Caliburn.Micro.Autofac for .NET 4 Fixed incorrect AssemblyInfo.cs values for all projects
I just released Caliburn.Micro.Autofac 1.2 to NuGet . Please see Introducing Caliburn.Micro.Autofac for usage. Version Notes Upgraded .NET 4 and Silverlight 4 versions to Caliburn.Micro 1.2.0 Created a psake build script to be used in Continuous Integration Added new sample applications First version of Windows Phone 7 support Known Issues with Windows Phone 7 Support The SimpleContainer class is not supported or exposed by the container The PhoneContainer class is not supported or exposed by the container The IPhoneContainer class is not supported or exposed by the container Exposed new Creators for the Windows Phone Bootstrapper CreateFrameAdapter CreatePhoneApplicationServiceAdapter CreateVibrateController CreateSoundEffectPlayer
I just released Caliburn.Micro.Autofac 1.1 to NuGet . Please see Introducing Caliburn.Micro.Autofac for usage. Version Notes Cleaned up source directories slightly Refactored AssemblyInfo.cs into GlobalAssemblyInfo.cs, VersionAssemblyInfo.cs, and project AssemblyInfo.cs Upgraded Autofac to version 2.5.1 Added support for Silverlight 4 I have also started working on making this library compatible with Windows Phone 7, so look for that in the near future.
Last year I wrote Bootstrapping Caliburn.Micro with Autofac and it has since become one of my most popular posts. While the code presented in the post worked at that time, wizbit and Craigology pointed out that it stopped working with newer versions of Autofac . I set out to do the minimum amount of changes to make it work with the newest versions Autofac and Caliburn.Micro . The Best Laid Plans That was the plan. It has been said that no plan survives first contact with the enemy. Once again that saying is proved true. Both Caliburn.Micro and Autofac were now available as Nuget packages. Given my ongoing goal to try and favor Nuget dependencies, I used them. That’s when I discovered Caliburn.Micro’s new default bootstrapper based on MEF . While I think this is a vast improvement over the original default, and I like the fact that it is included as part of Caliburn.Micro , it broke some of my default conventions. Specifically, I like to enforce a certain project structure when working with MVVM in which views are in a Views namespace, and ViewModels are in a ViewModels namespace. My Autofac bootstrapper enforced this. ...
Over the last few weeks I have been writing some in-depth articles for my Learning Caliburn.Micro series. Today is a brief side-discussion where I introduce a ReSharper File Template to help with the task of generating view-models. Background So why do you need this template? Simple – to write those twenty or so lines of code you constantly have to do yourself. I will warn you – this template is highly opinionated. It assumes that you when you create you view-models, you have the ability to pass the IEventAggregator as a parameter. I use Autofac as the way all my view-models are created, so it deals with this dependency injection for me. If you use MEF, then you will need to add the appropriate ImportingConstructor attribute. If you use ReSharper this is easy enough. Just edit the template after you import it. ...
It has been about two weeks since my last post in my Learning Caliburn.Micro series, so it far past the time for this post. Prepare the Project This post is going to focus on using the Autofac IoC with Caliburn.Micro. From the point of view of the framework it fulfills the same task as the MEF bootstrapper I discussed in Caliburn.Micro the MEFtacluar, or Rob discussed in Caliburn.Micro Soup to Nuts Pt. 2 – Customizing The Bootstrapper. The difference is that it uses Autofac instead of MEF. ...
Caliburn.Micro Logging Abstraction This post covers logging. Caliburn.Micro has a simple logging abstraction that consists of an ILog interface, and a LogManager class (see below). To add logging to any Caliburn.Micro project, you need to implement a class that extends the ILog interface, and you need to replace the delegate for GetLog. In this post, I will show you how to hook up a debug logger that logs to the Output window in Visual Studio, a log4net logger, and an NLog logger. For other loggers, it would be a simple matter to modify these examples to support them. ...
I was going to call this post ‘How I learned to stop worrying and love MEF .’, but I am not sure enough people would get the reference. Besides, it would put the focus too much on MEF , and not on Caliburn.Micro , which is the topic of the post. This is the second in my series of using Caliburn.Micro for WPF applications. The first post, Caliburn.Micro – Hello World, covered an introduction to setting up a project, and the basics of view and view-model interaction. This week I am going to introduce how to make your applications more loosely coupled by leveraging MEF . As this series progresses, we will be leveraging MEF more, so I wanted to cover it early on. ...