Home/ Questions/Q 8053509
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T07:52:10+00:00

I’m working on a Surface WPF project where we try to implement the MVVM

  • 0

I’m working on a Surface WPF project where we try to implement the MVVM pattern. Within this project we are building a few custom controls which we bind to different viewmodels.

For example we have a settings control which has a settings viewmodel and we have a mainviewmodel which is the “overall” viewmodel.

In our surfacewindows.xaml page we are setting the datacontext to the main viewmodel by using the viewmodel locator in mvvm-light. Also on our surfacewindow.xaml we have added our settings control and on the control we have set the datacontext to the settings viewmodel.

Now we need both viewmodels to interact with each other: The current case is that we need to set the visibility of the settings control. We have a property on the main viewmodel that is a boolean (IsSettingsControlVisible) which is bound to the controls Visibility property by using a converter to convert the boolean to a visibility object.

The problem arises now when we need to set the visibility to not visible by clicking on a close button on the settings control. Because we have set the datacontext on the control to the settings viewmodel, we cannot access the mainviewmodel.

What we have thought of until now is adding the settings viewmodel as a property to the mainviewmodel and remove the datacontext from the settings control. In the settingscontrol we will than use the binding as SettingsProperty.Property. Than we can access the mainviewmodel too from the setttings control. Does that make sense? Are there better ways of doing these kind of interactions?

I really like to hear your ideas about how to make these interactions happen.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I tend to work with graphs of view models that are constructed using Castle Windsor. The top level view model uses constructor injection to receive the next level of view models that it requires. And in the views I bind content presenters to properties on the view models to create the corresponding view graph.

    Doing this, it’s quite easy for parent child view models to communicate, but a bit harder for sibling or more distant view models to communicate.

    In these instances, I tend to use an event aggregator, or Messenger to allow the view models to communicate.

    • 0