search

MarimerLLC / cslaforum

Discussion forum for CSLA .NET
https://cslanet.com
Other
31 stars 6 forks source link

Getting Started With Caliburn.Micro #490

Open CrossSlide opened 6 years ago

CrossSlide commented 6 years ago

I want to use Caliburn.Micro on a WPF project. I'm new to MVVM and have only studied the Bxf framework in book 4.

I'm also looking to use CslaContrib-Caliburn.Micro.V2.WPF. It says it's for v2 of Caliburn.Micro. Do I need to find the Caliburn.Micro v2 or can I use the latest Caliburn.Micro v3.2?

tfreitasleal commented 6 years ago

Good point. I guess the partt of Caliburn.Micro we need didn't change, but I'm not sure. Please try and report back.

CrossSlide commented 6 years ago

Thanks @tfreitasleal, I'll try and report back but it may be a while. It's all new to me...

CrossSlide commented 6 years ago

Hi @tfreitasleal, Is there any sample code out there or documentation on how to use CslaContrib-Caliburn.Micro.V2.WPF?

tfreitasleal commented 6 years ago

None that I knwo of. I have an incomplete sample I can send you. Email me tfreitasleal gmail so I can zip it to you.

Chicagoan2016 commented 6 years ago

@CrossSlide , If you get some down time, please share your experience with us, I had looked at Prism in the past but didn't actually integrate it with CSLA. Thanks

CrossSlide commented 6 years ago

@Chicagoan2016, So far I really like it. @tfreitasleal has also been a big help. I don't have a truly functioning app yet but I'm on my way. I have not found any problems with Caliburn.Micro v3.2 and CslaContrib-Caliburn.Micro.V2.WPF working together so far. Overall I'm please with the combination.

tonydrake commented 6 years ago

Agree - please share (a blog erc) - I spent time with Caliburn Micro, and MVVMCross, but found MVVMLight the only one what worked for me... and I had to work around some oddities in CSLA to make the experience real for users (autosave on data change, and I still get inconsistent error flagging). There is an issue with MVVMCross where you cannot re-validate a view (it shows with calling any event you can hook into) before you show to a user (views are singletons) so you can't load a fresh dataset in a detail after the initial create) which killed it for me, but CM never wanted to play at all with valid/dirty objects and error management. I would love to get CM working, but xamerin/aspnet core is more important to me now...

On 24 February 2018 at 05:53, CrossSlide notifications@github.com wrote:

@Chicagoan2016 https://github.com/chicagoan2016, So far I really like it. @tfreitasleal https://github.com/tfreitasleal has also been a big help. I don't have a truly function app yet but I'm on my way. I have not found any problems with Caliburn.Micro v3.2 and CslaContrib-Caliburn.Micro.V2.WPF working together so far. Overall I'm please with the combination.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/MarimerLLC/cslaforum/issues/490#issuecomment-368113229, or mute the thread https://github.com/notifications/unsubscribe-auth/ABtKPsczAMCdmU5WYJqu0mGnlVC0EdiBks5tXxBMgaJpZM4R1408 .

rockfordlhotka commented 6 years ago

@tonydrake you might find that version 4.6 helps, because it supports in-place editing of an object graph. Or more accurately, it supports merging the result of a Save back into the original graph, rather than rebinding the UI to a new object graph.

  var merger = new Csla.Core.GraphMerger();
  merger.MergeGraph(obj, obj.Save());

I added the GraphMerger type, though I'm not 100% sure I like the interface the way it is - so feedback is welcome.