This looks very similar to the recommended practice in the Wrox Professional ASP.NET MVC book, the first chapter of which is available for free from the above URL. Starting on page 100 they have a section on ViewData and ViewModels. When a Controller class decides to render an HTML response back to a client, it … Read more
The preferred way since .Net 4.5 to implement data validation is to let your view model implement INotifyDataErrorInfo (example from Technet, example from MSDN (Silverlight)). Note: INotifyDataErrorInfo replaces the obsolete IDataErrorInfo. The new framework infrastructure related to the INotifyDataErrorInfo interface provides many advantages like support of multiple errors per property custom error objects and customization … Read more
Where do I put my validation code? On the view models you should validate everything that’s specific to the application like for example the date should be in en-US format culture, …. I need to add code to map between business objects and view models. That’s why there are tools such as AutoMapper. Different problems … Read more
From Jimmy Bogard: CreateMap<Foo, Bar>().ForMember(x => x.Blarg, opt => opt.Ignore()); It’s in one of the comments at his blog. UPDATE(from Jamie’s comment Jan 4 ’19 at 11:11:) Ignore has been replaced with DoNotValidate in ForSourceMember: https://github.com/AutoMapper/AutoMapper/blob/master/docs/8.0-Upgrade-Guide.md
Absolutely, positively NO Your UserControls should NOT have ViewModels designed specifically for them. This is, in fact, a code smell. It doesn’t break your application immediately, but it will cause you pain as you work with it. A UserControl is simply an easy way to create a Control using composition. UserControls are still Controls, and … Read more
You need to have a factory class for your ViewModel. public class MyViewModelFactory implements ViewModelProvider.Factory { private Application mApplication; private String mParam; public MyViewModelFactory(Application application, String param) { mApplication = application; mParam = param; } @Override public <T extends ViewModel> T create(Class<T> modelClass) { return (T) new MyViewModel(mApplication, mParam); } } And when instantiating the … Read more
“View Model” is just a pattern. There’s nothing magical about the name, but generally any class being passed to a view (whether for simply displaying data or for the purposes of form submissions) is referred to as a “view model” and given a name like FooViewModel or FooVM to indicate that it’s part of that … Read more
Essentially Model and View Model are both simple classes with attributes. The main objective of these classes are to describe (to “Model”) an object for their respective audiences that are respectively the controller and the view. So you are completely right when you say To my understanding, it’s a kind of Model that has a … Read more
The delegate method used in this and the linked answer can be used in any parent-child relationship and in either direction. That includes from a child view model to a parent view model, a Window code behind to the code behind of a child Window, or even pure data relationships without any UI involved. You … Read more
Assuming you have the following models: public abstract class TableInputModel { } public class RectangleTableInputModel : TableInputModel { public string Foo { get; set; } } public class CircleTableInputModel : TableInputModel { public string Bar { get; set; } } And the following controller: public class HomeController : Controller { public ActionResult Index() { var … Read more