Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • by "subscribes to the events on the ViewModel", do you mean the events of the model change? Commented Sep 27, 2017 at 15:13
  • Sorry, I meant "Model." Commented Sep 27, 2017 at 15:14
  • Out of curiosity, why is the Model firing events? Commented Sep 27, 2017 at 15:15
  • classic notify PropertyChanged event Commented Sep 27, 2017 at 15:25
  • I've updated the question with an implementation based on your suggestion. I provided another re-direction for the setting the properties through this intermediate class with an intention of moving Model validation and other any business logic performed at the ViewModel to the domain/business layer. This modification enables me to provide a reusable validation framework of the Model to other layers (UI and others). Any thoughts on this? Commented Sep 29, 2017 at 10:08