When using custom dialog window in an MVVM application, do you think that using code to handle properties Okay for the event, etc.? Or should I always turn off a View Module in every dialogue scene? What's your idea
The code-behind or not, what criteria will we fix?
What if the custom dialog is a complex wizard? What if the dialog is a complete mini-application, so would it be right? In those cases, I think we can argue that MVVM is suitable, and code-behind is not really very attractive.
If we accept it, then where do we draw the line? I think we should not do this, because a dialogue that is simple today can be complicated in the future It would be better to be consistent.
In other words: MVVM all the way
Also see related questions:
Comments
Post a Comment