Comments on: How to close a View from a ViewModel ?

By: Jeremy

Jeremy — Mon, 01 Mar 2010 22:10:39 +0000

Rob,

As I said at the end of the post, this is a very basic implementation. If you need more sophisticated features you would have a dedicated service to manage lifetime of Window. You can take a look at the Calcium framework.

By: Rob

Rob — Tue, 02 Feb 2010 22:43:45 +0000

This doesnt really help though when the VM is behind a user control somewhere down the visual tree, which is more likely. How would you get the event fired from this VM to bubble up to the window that contains the usercontrol which has this Vm as its datacontext?

By: Jeremy

Jeremy — Wed, 27 Jan 2010 11:59:26 +0000

I think you could use a Behavior that execute a command whenever a Window is closing. In the command target you could use some kind of “DialogService” to find a service which would open the dialogbox for you

By: Daniel Skinner

Daniel Skinner — Wed, 27 Jan 2010 10:58:05 +0000

Regarding closing the window with the X: What if we need to show a save changes dialog for example?

By: JAPF » Blog Archive » Review of 2009 blog posts

JAPF » Blog Archive » Review of 2009 blog posts — Wed, 06 Jan 2010 19:02:34 +0000

[...] How to close a View from a ViewModel ? [...]

By: Jeremy

Jeremy — Tue, 20 Oct 2009 08:09:04 +0000

Well in this case the closing procedure is handled by WPF itself right ? What do you want to do in particular ?

By: arconaut

arconaut — Mon, 19 Oct 2009 16:19:24 +0000

Thanks for this useful post!
But how would you handle closing of a window when user clicks the default window’s Close button? (“Red X”)

By: Bob Bartholomay

Bob Bartholomay — Tue, 29 Sep 2009 20:29:05 +0000

I blogged about a similar (same?) forum post a few days ago and my research revealed few alternatives that may be of interest see: http://blog.flexforcefive.com/?p=206

By: Jeremy

Jeremy — Tue, 29 Sep 2009 17:48:50 +0000

Thomas,

Yes, as always an attached property can always comes to the rescue to clean up our code

Mike,

Ok now it makes sense. Thanks for your details !

By: Mike Strobel

Mike Strobel — Tue, 29 Sep 2009 17:27:33 +0000

Well, I use a somewhat different pattern that I call PMVP (Presentation Model-View-Presenter), so my suggestion may not be appropriate for MVVM. You can think of PMVP as MVVM with the ViewModel broken up into two separate entities: a Presentation Model encapsulating the data model, UI state information, change notification, and commands; and a Presenter, containing the UI logic (a sort of controller for the view).

My Presenter classes generally have Run() and Terminate() methods, which (among other things) call OnCreated and OnDestroyed methods on the View. In this pattern, the CloseCommand in the PM would be handled by the Presenter, which would either terminate itself or raise a termination request event to some higher-level entity like an application controller, task director, etc.