Yesterday, I finally added my Castle Windsor's Adapter for Prism under CompositeWPFContrib project. To download the complete source plus unit tests go to the project's page here. Wiki page on how to use Windsor adapter with Prism is also being created.One small thing you should know before compiling the source code, specially if you're downloading the source using SVN or Codeplex client, is that you need to have windows Maximum Path Length limitation of 256 characters in mind. So, create a folder in root of your hard-drive and place the solution's files there, because project and folder names in CompositeWPFContrib 

The other day, I was working on the WPF application that I'm spending my spare time with. I've been trying to make improvements to startup time of the application's cold-start. With all the improvements done, I thought it'd be a good idea to add a splash screen and show the user about the loading progress. It is relatively easy to setup a splash screen for a WPF application and in fact, I've done that before. But in this application I'm using Prism framework, which if you do not already know, is a WPF Composite Application framework.Prism itself has some initialization 

I've became one of the developers on CompositeWPF Contrib project. I will add my Windsor adapter which lets you choose Castle Windsor dependency injection container when you're working with CompositeWPF (formerly Prism). Hopefully, you can download the new extension directly from the project's page on Codeplex. Later I'll add some more samples and demo projects to the code base. Your feedbacks and comments on this is very much appreciated.  

In my previous post, I discussed how I had to move to Prism. The problem was that I had a code base which I now should use Unity container instead of Windsor. I had a look at the drop provided by P&P team that uses Windsor container, but the source code used is from an older version, So, I had to do it myself. Actually, it is relatively easy to use other containers with Prism. You need to create a BootStrapper and a Container Adapter.If you need to use Prism with Windsor container and Log4Net, here is the complete source 

I was using Caliburn framework on a pet project of mine for the last couple of weeks. At some point of time, when I merged my custom made styles, application did not open views anymore, complaining something is wrong with my styles. I spent a lot of time to figure out what is wrong, but found nothing, except if I do NOT use custom styles everything is working fine (Maybe that IS a proof of my styles having some error!).So, I decided to port the application to Prism (now called Composite WPF). How smooth was the port procedure, you might