Multiple Window (Views/ViewModels) Generation Strategy

Question

I am using C#, .Net WPF and MVVM approach

What would be a recommended strategy/Design for the situation were I have a MainWindow view and associated viewmodel and wish to "open" another such window for the user which will display another objects values. For example they are viewing an objects values via mainwindow then go into a search feature where they find another object for which they want to view its values. they click on this in the list and a view appears showing that objects values. they then can close this view and return to the original view with the original object.

First I have at least 2 choices Im aware of I can begin with. Use the existing MainWindow view and viewmodel for the new object as they are exactly the same or 99% same and need to use same view/viewmodel functionality or write a (almost) copy of the mainwindow view/viewmodel and show this one. The second option will require more maintenance because I have to duplicate any changes across both but can make other things easier and maybe cleaner.

So whats best approach for this issue?

The next decision to make is how to do this? I have so far considered the following ways to do the "showing" of the new view and selected objects data.;

set up datatemplates in the mainwindow and swap the views in and out (ie triggered by xaml button command bound to viewmodel)
instantiate a new instance of MainWindow view and mainwindowviewmodel using .ShowDialog in code (ie triggered by xaml button command bound to viewmodel)
Set up a view factory instead of instantiating in code

In all cases I need to pass a parameter to the newly shown View or Dialog that is used by its ViewModel to retrieve from database and show the required object.

thanks Scott

Answer

I make a demo on my understanding for your question, please check if I misunderstand. If I misunderstand, could you please give an operation result diagram to anlayze?
The ViewModel is:

class PersonViewModel:NotifyObject  
    {  
        private PersonModel userEdit;  
        public PersonModel UserEdit  
        {  
            get { return userEdit; }  
            set  
            {  
                userEdit = value;  
                OnPropertyChange("UserEdit");  
            }  
        }  
  
        private ObservableCollection ltPersons = new ObservableCollection();  
        public ObservableCollection LtPersons  
        {  
            get { return ltPersons; }  
            set  
            {  
                this.ltPersons = value;  
                OnPropertyChange("LtPersons");  
            }  
        }  
  
        public PersonViewModel()  
        {  
            LtPersons = new ObservableCollection() {   
                new PersonModel { Name = "John1", Age = 11, Pass=false,Email= new Uri("mailto:JOE+@school.com") },   
                new PersonModel { Name = "John2", Age = 12 , Pass=false,Email= new Uri("mailto:JOE+@school.com")},   
                new PersonModel { Name = "John3", Age = 13 , Pass=false,Email= new Uri("mailto:JOE+@school.com")} };  
        }  
  
        public ICommand ButtonCommand  
        {  
            get  
            {  
                return new DelegateCommand((model) =>   
                {  
                    UpdateUser updateUser = new UpdateUser();  
                    updateUser.DataContext = model;  
                    updateUser.Show();  
                });  
            }  
        }             
    }

The MainWindow is:

The UpdateWindow is:

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Multiple Window (Views/ViewModels) Generation Strategy

1 answer