Answer the question
In order to leave comments, you need to log in
Is using Caliburn.Micro justified?
Hello!
I study WPF recently, but I managed to write one simple accounting application, so to speak, on the "naked" WPF. The company had a question of using Caliburn.Micro in a new project. I compared it with other frameworks (the competitor is MVVM Light in my opinion). By examples, I wrote a couple of HelloWorlds. As a result, questions only increased:
1) It turns out that its whole point is in the simplicity of binding the ViewModel to the View?
2) By its search for properties from the ViewModel for x:Name, is performance lost and how much?
3) As I understand it, this framework uses events instead of commands. What about performance?
Thank you in advance!
I will be glad to advice on the whole topic.
Answer the question
In order to leave comments, you need to log in
1. Essentially - yes. This is his main "feature".
2. Yes, it is lost, but not significantly. I do not remember, somewhere came across benchmarks.
3. I can't say anything about this. I do not remember.
You can see this recent comparison here: sonyks2007.blogspot.ru/2015/04/most-popular-mvvm-f...
PS Personally, I liked MVVM Light more. Although there are coroutines in Caliburn.Micro.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question