Hello all,

I'm looking into using Caliburn for the first time. I know the general advice seems to be to go for Caliburn Micro, but the thing that has attracted me to Caliburn is the AOP/Async actions.

So the decision is between 1.1 and the trunk, and I would appreciate answers to the following:

1) The docs are (I presume) for 1.1. How difficult will it be getting going with v2 because of this?

2) How stable is the trunk?

3) What are the main missing features or disadvantages of sticking with 1.1?

many thanks,

Jordan.

You can easily add the AOP style filters and async actions to Caliburn.Micro, if that is your only reason for wanting Caliburn. Here's how http://caliburnmicro.codeplex.com/wikipage?title=Action%20Filters&referringTitle=Documentation

I strongly recommend that you use Caliburn.Micro.

That said, if you still want to stay with Caliburn, I recommend you use the Trunk. It is very stable and will be going to a Release Candidate very soon. There are now separate docs for v2 here http://caliburn.codeplex.com/documentation They are still in progress though. You can however, read a brief list of differences in the frameworks there. The thing to remember is that Caliburn.Micro is pretty extensible and it's often easy to add the things that are missing if you really want to. All you have to do is scour the Caliburn.Micro forums and look at the recipes section of the docs to see some examples of what people are doing.

Hi,

Thanks for the quick reply.

I'll definately look at adding async actions to micro as suggested in the link. However, I'm probably going to pushed for time on my next project, so I'd really like to use something that just works. Also, I presume the solution suggested is prone to breaking in future if Caliburn.Micro changes?

thanks again,

Jordan.