Those who have followed Caliburn over the past 6-8 months have probably heard alot about Caliburn.Micro as well. Whenever somebody has tweeted about getting started with Caliburn, Rob Eisenberg has quickly guided them to Caliburn.Micro. You don’t need to be a rocket scientist to figure out that he has his reasons!Even though I have had the suspicion that Caliburn will be stopped and that Caliburn.Micro is the future, I have never yet seen this written out. That was until this weekend when Rob Eisenberg added the following comment on the Caliburn discussion forum:
if you haven’t started working on it, I recommend that you do not use Caliburn. You should be using Caliburn.Micro instead. After the release of Caliburn, there will be no further releases except to fix any large bugs that appear. Caliburn.Micro will continue to evolve though. You will find that you can do almost everything you would need in Caliburn.Micro and it is pluggable enough to add the things you can’t do. It has a much larger community and will have better support. In other words, you should consider Caliburn to be a legacy framework only used on applications which were previously built with it. New applications should be built with Micro.
I am not at all surprised and I frankly don’t feel very afraid Those of us who already use Caliburn need to make the shift to Caliburn.Micro, but in most cases this will be just a minor job! The upgrade from Caliburn 1.x to Caliburn 2.0 will involve some work, so I rather recommend investing this time in a Caliburn->Caliburn.Micro shift instead on a pure Caliburn upgrade to version 2.0!
Visit http://caliburnmicro.codeplex.com/ for more details on Caliburn.Micro!