What is the main goal of MVVM pattern? [closed]
Closed 10 years ago.
Again MVVM / MVP story , passing interface of a view to its view model why it is bad?
I have used WPF for an Enterprise solution (hundreds views heavily used Data inputs and validation) in MVP pattern (it was a clean solution usually small amount of code behind forms and main code was in pretension layer which we called it user interface process or UIP layer )
Again MVVM / MVP story , passing interface of a view to its view model why it is bad?
I have used WPF for an Enterprise solution (hundreds views heavily used Data inputs and validation) in MVP pattern (it was a clean solution usually small amount of code behind forms and main code was in pretension layer which we called it user interface process or UIP layer )
Again MVVM / MVP story , passing interface of a view to its view model why it is bad?
I have used WPF for an Enterprise solution (hundreds views heavily used Data inputs and validation) in MVP pattern (it was a clean solution usually small amount of code behind forms and main code was in pretension layer which we called it user interface process or UIP layer )
Again MVVM / MVP story , passing interface of a view to its view model why it is bad?
I have used WPF for an Enterprise solution (hundreds views heavily used Data inputs and validation) in MVP pattern (it was a clean solution usually small amount of code behind forms and main code was in pretension layer which we called it user interface process or UIP layer )
How to use data shaped by the UI from the ViewModel while keeping concerns separated?
I’m coming from a winforms background and trying to get ahold of MVVM and XAML. Right now I’m wondering how I can take advantage from a data-shaping control (either native or provided by a third party) while maintaining separation of concerns intact.
What is better to return from the DataService: Status or Exceptions?
I have a MVVM app with DataServices (using mvvmlight).
Best Practice Method for Including Images in a DataGrid using MVVM
All, I have a WPF DataGrid. This DataGrid shows files ready for compilation and should also show the progress of my compiler as it compiles the files. The format of the DataGrid is
Encapsulate multiple properties into a single class to use as a custom DependencyProperty
My application is a WPF project implemented in C# .NET (4.5) using an MVVM architecture with no code-behind in the View. In order to eliminate the coupling between the View and the ViewModel I’m implementing some of the WPF-specific behaviours as custom DependencyProperties that can be bound to ‘simple’ properties exposed by the ViewModel.
Encapsulate multiple properties into a single class to use as a custom DependencyProperty
My application is a WPF project implemented in C# .NET (4.5) using an MVVM architecture with no code-behind in the View. In order to eliminate the coupling between the View and the ViewModel I’m implementing some of the WPF-specific behaviours as custom DependencyProperties that can be bound to ‘simple’ properties exposed by the ViewModel.