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 have recently needed to rebuild my Continuous Integration server, and once more found out that I never documented my configuration the last time I set it up. The same has happened every 18 months or so, when I rebuild my development machine. Having wasted hours re-discovering the list of tools I need to have installed, and the options I always consider and discard, I have decided to be inspired by Scott Hanselsman’s Ultimate Developer and Power Users Tool List For Windows and make my own list.
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.
Continuing my current mission to NuGet-ify my current utility libraries, and building on my Introducing Caliburn.Micro.Logging post, I have now released Caliburn.Micro.Logging.NLog which integrates log4net into Caliburn.Micro. There were no code changes to this from the code in my earlier post How To Do Logging with Caliburn.Micro, so it should be very easy to migrate to the NuGet package.
How to Use Caliburn.Micro.Logging.NLog Using NuGet for Caliburn.Micro.Logging.NLog The NuGet package id is Caliburn.
Continuing my current mission to NuGet-ify my current utility libraries, and building on my Introducing Caliburn.Micro.Logging post, I have now released Caliburn.Micro.Logging.log4net which integrates log4net into Caliburn.Micro. There were no code changes to this from the code in my earlier post How To Do Logging with Caliburn.Micro, so it should be very easy to migrate to the NuGet package.
How to Use Caliburn.Micro.Logging.log4net Using NuGet for Caliburn.Micro.Logging.log4net The NuGet package id is Caliburn.
In the spirit of continuing to NuGet my extensions, I decided to try and create a NuGet package for log4net and nlog. However, I still found my System.Diagnostics.Debug logger to be useful, and did not want to include it twice. This led me to do a quick refactoring of the logging code from How to do Logging with Caliburn.Micro to create a new assembly Caliburn.Micro.Logging which would include the common code between the log4net and nlog loggers.
A few years ago I wrote Type Tracking Extension for Unity and Extending and Demonstrating the Type Tracking Extension for Unity, and while I have been using Autofac more, I felt this code was due for a slight update. Given the ease of creating a NuGet package for Caliburn.Micro.Autofac (see Introducing Caliburn.Micro.Autofac), I thought that I could give some Nuget love to the Type Tracking Extension for Unity.
What’s Changed Obviously, if I am working on some changes, I might as well bring the code up to date.
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.