Caliburn.Micro.Logging for NLog and log4net Updated

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:

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

Caliburn.Micro.Autofac 1.2.1 Released

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

Caliburn.Micro.Autofac 1.2 Released

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

Introducing Caliburn.Micro.Logging.NLog

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.

Introducing Caliburn.Micro.Logging.log4net

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.

Introducing Caliburn.Micro.Logging

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.

Managing Dependencies with NuGet

Note: This was presented to the Tampa C# Meetup on April 6th, 2011. Most large .NET projects will use a number of libraries and frameworks. Those dependencies of your project will have their own dependencies. To make it more complex, those libraries may depend on other libraries, and in some cases – on each other. The Dependency Management Problem The dependency problem is something that strikes fear into the heart of many a developer, and even more in to the lead or manager.