Home/ Questions/Q 636107
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T20:28:45+00:00

Using the Composite Application Guidance tools from Microsoft, It seems as if there is

  • 0

Using the Composite Application Guidance tools from Microsoft, It seems as if there is no mechanism to allow you to query your modules ViewModels and ask if any of them have unsaved data. This is a problem because, and I’m guilty of this as well, you cannot stop the application from terminating when there is unsaved data…

I had thought about creating an interface called IApplicationEvents and have an event on there called ApplicationExiting. The thought being that each module can subscribe to the event and, when fired, can send back a “Cancel=true” or “Cancel=false” to say whether or not to allow the application exiting.

Curious to find out what others may have done in this instance, and to see what possible solutions there are in the community to solve this issue.

Thx.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are a lot of choices here.

    First off, I wanted to clarify a little nomenclature… typically your Views or ViewModels contained within your Module assemblies are the things with unsaved changes, not the Module itself. The Module is responsible for instantiating any views necessary at the start and contributing back to the shell during Initialize and that’s typically it, so when you attack this problem, you’ll want to focus on your views/viewmodels and not the Module classes.

    Options off the top of my head:

    1. Adopt a complimentary framework like Caliburn that has support for application events like this (as well as some MDI events like ViewClosing, that kind of thing). It has builtin support for Prism (http://caliburn.codeplex.com/)

    2. Use a composite command. Your views or viewmodels will register themselves with a composite command elsewhere (CloseCommand, which you declare statically for your application) and every open view will have its CanExecute and Execute methods fired so that you can both vote in the closing of the application and also react to it, should it happen anyway. CompositeCommands are a feature of Prism. (See: Commanding Quickstart)

    I think those are probably the most elegant. There’s a few more options but these live in the best harmony with existing conventions.

    Hope this helps.

    • 0