I would prefer option 1 and not have to use a wait cursor. I really dont want to lock the UI thread. Can you enlighten me on option 1?
On Oct 1, 9:21 am, José F. Romaniello <[email protected]> wrote: > I think that this is a common question and diserves a separated thread. > This question come to my private inbox, but the autor agreed to move the > nhusers list. > > 2009/10/1 justin coon <[email protected]> > > > > > Hello Jose & Chris, > > > Ive been following a thread on the nhusers google group about WPF BG worker > > and nHibernate. Basically what im trying to do is .Refresh() my activerecord > > business objects after sending out a Mediator message. This was working > > until i noticed that it was freezing my UI during the Refresh. So i decided > > to try and kick off a background worker(when the message is received in a > > ViewModel) and do the Refresh inside that. And thats when i ran in to > > problems...errors....Session is gone, etc, etc. I sort of understand why, > > cause I go out on a different thread and try and refresh my object and then > > the session is gone when the thread work completes (this is somewhat correct > > i believe). Im praying that one of you gurus can help me to multithread > > castle AR/nhibernate inside a WPF app. This is a huge limitation for me and > > others as well. Please please please shed some light on this for me? > > > Thanks so much > > Justin Coon > > Software Engineer- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
