viewmodel

I am using Entity Framework 4.0, and making use of POCO objects. When I populate POCO objects from the DB, I translate property values to my own Domain objects, which we can call my Model. Necessarily, whether or not the fields of my Model are Nullable depends on whether the value it maps to in the database comes from a NULL or NOT NULL column. I won't go into detail, but the values must be nullable in the DB, because a user can partially save a draft of the object before publishing it to the public. That being the case, I have several fields that are nullable. So let's say my model looks like

I have created a viewmodel public VMPosition { public VMPosition(){}//for model binder public VMPosition(int EmployeeID) { PositionStatusList = new SelectList(_repo.getStatuses); //populate other properties } public int CurrentPositionID { get; set; } public int EmployeeID { get; set; } public int CurrentPositionHistoryID { get; set; } public bool AddingNew { get; set; } public bool ClosingCurrent { get; set; } public string CurrentPosition { get; set; } public DateTime CurrentPositionStartDate { get; set; } public string ReasonForDeparture { get; set; } public SelectList PositionStatusList {

I have a viewmodel which needs data from two models person and address: Models: public class Person { public int Id { get; set; } public string Name { get; set; } public int Age { get; set; } public int Gender { get; set; } } public class Address { public int Id { get; set; } public string Street { get; set; } public int Zip { get; set; } public int PersonId {get; set; } } The Viewmodel is as such public class PersonAddViewModel { public int Id { get; set; } public string Name { get; set; } public string Street { get; set; } } I have tried several ways to get data into the viewmodel and pass

I've been using ASP.net MVC for about two years now and I'm still learning the best way to structure an application. I wanted to throw out these ideas that I've gathered and see if they are "acceptable" ways in the community to design MVC applications. Here is my basic layout: DataAccess Project - Contains all repository classes, LINQ-to-SQL data contexts, Filters, and custom business objects for non-MS SQL db repositories (that LINQ-to-SQL doesn't create). The repositories typically only have basic CRUD for the object they're managing. Service Project - Contains service classes that perform

I am wondering is it good practice to try to make a view that takes in a generic view model? I am wondering this because someone mentioned that he was anticipating to have to do lots of duplicate code unless he started to make a generic view and generic view model. So basically the views would be like just a set of controls. One view might have 2 controls(say a text-box and radio button) another view might have 50 controls on it. They will all have the same look and feel(it just grows by number of controls) . Basically he was thinking having a view model takes in the object(domain object)

In my ASP.NET MVC 2 (RC) project - I'm using AutoMapper to map between a Linq to Sql class (Media) and a view model (MediaVM). The view model has a SelectList property for a drop down in the view. I have a custom value resolver to populate the SelectList property items from the db, but am wondering if there's a way to pass a couple values from the source model into the resolver (using ConstructedBy method?) to a) define the selected item and b) filter the items from the db. The source object gets passed into the custom resolver - but the resolver is used on several different view models with

I am using automapper to map my models to viewmodel classes to pass to my view. My question really is where should the validation go? I was planning on using the MetaData decorations - a feature of mvc 2. But either in the model or viewmodel? Or in both places? Validation should be done minimum at the View Model because this is what you receive as action argument and contains the user input. You could also have validation at the model. My answer would be ViewModel because Model can change (for example from using Linq2SQL to EF). This way when you plug another Model you still have your

I am using MVVM Light and have used the packaged messenger system to communicate between view models, however I have hit a bit of a dilemma! Basically when a user clicks on a customer record the corresponding view is opened and with it the CustomerViewModel is instantiated. At this point the CustomerViewModel requires the selected customers ID from the previous view model ( ViewAllCustomersViewModel ) so that it can get selected customers info which the view binds to (still following?). So initially my thought was too send that ID in a message from the ViewAllCustomersViewModel (where the