4

I'm using EF 4.1 Database First approach, with T4 template generating my POCO classes in separate assembly. I have repositories for fetching data, and service layer which is used for communication with UI.

I was trying to make cascading dropdowns. I'm new in MVC and EF 4.1, so I searched stackoverflow for possible solutions.

This is sample viewmodel class:

public class MyViewModel
{
public int CustomerId { get; set; }
public string CustomerName { get; set; }
public IEnumerable<Phone> Phones { get; set; }
}

What I have read so far, solutions are:

  1. Use ScriptIgnoreAttribute in System.Web.Script.Serialization on referencing properties - I don't really want to do this, because I don't want to add reference to System.Web in my POCO project

  2. Disable Lazy Loading in EF 4.1 DbContext - I'm not sure do I want to use Include thorough my project

  3. Return anonymous types - will I have problems with this approach when my project gets big?

  4. Use a ViewModel - suppose I have a Customer which can have 1 or more phones. In first dropdown list you can select Customer, and in second dropdown you display all of his phones.
    But wouldn't this generate a circular exception on my Phones object? Or i would make a special class for my Phone object? That seems like a lot of unnecesarry code.

  5. Use AutoMapper - don't have experience with AutoMapper, so I don't know how complicated it is.

For which one would you vote and why?

leppie
  • 115,091
  • 17
  • 196
  • 297
Marko Tošić
  • 92
  • 1
  • 2
  • 9

1 Answers1

5

Use a view model and AutoMapper to map between your domain models and the view model which you will be sending to the view. This way you have total control over what properties are sent to the view which as a consequence reduces the amount of data sent between the server and the client. Also because now you are using view models your code is more resilient to modifications in your domain entities. If you modify them, only the mapping layer will be affected and thus you will not ever need to touch to your controllers or views.

So my advice is to download AutoMapper, read the documentation and start using it. It's a life changer, believe me.

just.another.programmer
  • 8,579
  • 8
  • 51
  • 90
Darin Dimitrov
  • 1,023,142
  • 271
  • 3,287
  • 2,928
  • Could I use my sample class as viewmodel? Would I have circular reference serialization problem with Phone entity(also POCO generated from EF 4.1). – Marko Tošić Jul 08 '11 at 10:24
  • @Marko Tošić, what you have is not a view model as it contains references to your domain model (Phone). It's some hybrid and if this Phone class itself has references to other domain models you will quickly end up with the same problem. Don't do this. Define a pure view model class. – Darin Dimitrov Jul 08 '11 at 10:28
  • So I would have to define a DTO PhoneDTO class for my Phone model object class, and then have IEnumerable property in my ViewModel? I was trying to find an "easier" solution, but in the end, this seems like right approach. P.S. sry, I don't have enough rep for vote up. – Marko Tošić Jul 08 '11 at 11:03
  • @Marko Tošić, yes, but I would call it PhoneViewModel instead of PhoneDTO. – Darin Dimitrov Jul 08 '11 at 11:04