WPF Child Window with MVVM Design Pattern

In this article I'll discuss how to develop reusable WPF child window using MVVM designed pattern.Prerequisites :1. Basic Knowledge of MVVM Design Pattern.2. Basic Knowledge of Action<T> Delegate in C#.3. Basic Knowledge of XAML development.4. Visual Studio 2013 (You can use anot

C# (888.2 KB)
5,822 times
Add to favorites
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question

  • 555-555-0199@example.com
    1 Posts | Last post October 13, 2017
    • 555-555-0199@example.com
  • View Model in another class library
    1 Posts | Last post July 02, 2016
    • Hi Erandika Sandaruwan,
      Very nice artical.
      Question i have is how will we implement the ChildWindowView class if we have separate class library for ViewModels.
      Looking forward to your positive reply.
      Thanks in Advance,
  • Why I can't provide multiple popups?
    1 Posts | Last post January 02, 2016
    • I'm trying to implement popup call from popup, solution looks nice and thats what I need, but the thing is that I need call another popup(child) from popup(parent). I don't get any errors, just that the parent popup is closing, disappears, while calling another child popup from that parent popup. In solution noticed that there in ChildWindowManager class is singleton, maybe that affects it somehow. How can I fix it, that I call another popup(child) from popup(parent) without closing parent?
  • Why is ChildWindowView so strange?
    1 Posts | Last post July 03, 2015
    • I'm puzzled by your implementation of "ChildWindowView", which seems to be an orphaned "piece of code". It feels to me like an artificial way of avoiding putting that code into the "code behind" for the AddUserView.xaml, which I think in this case would make the code easier to understand? When I see a "new somethingView()" in a program, I immediately look for a "somethingView.xaml", but in this case there isn't one (ie there's no ChildWindowView.xaml), there just a fairly laborious journey through the ChldWindowView class which then instantiates a new AddUserView, and a ne AddUSerViewModel, and hooks them up.
      Am I missing the point maybe?