asp.net mvc automapper using

Question

recently i've started to use viewmodels with automapper. the problem appeared immediately. for example, i have such classes:

public class Zone
{
    public int ZoneId;

    public string Title;

    public int BannersCount;
}

public class ZoneView
{
    public int ZoneId
    {
        get;
        set;
    }

    public string Title;
    {
        get;
        set;
    }

    [Required(ErrorMessage = "Поле Кол-во баннеров является обязательным.")]
    [Display(Name = "Кол-во баннеров*")]
    public int BannersCount
    {
        get;
        set;
    }
}

and i don't want to edit Title in my view. so there i show Title not in TextEditor but so:

@Model.Title

and then in my POST action ZoneView comes with empty Title:

public ActionResult Edit(ZoneView zoneView)

after this i map it to domain model:

var zone = zonesRepository.Get(zoneView.ZoneId);
Mapper.Map<ZoneView, Zone>(zoneView, zone);

and after this in zone there is empty Title. What is the best way to act in this case?

@SLaks, because i don't want user to edit Title - only to display it. so it is not placed in TextEditor. — donRumatta
– donRumatta, Commented Dec 14, 2011 at 14:39

moribvndvs · Accepted Answer · 2011-12-14 14:39:22Z

2

You can create a mapping definition, instructing automapper to ignore the Title property when pushing values into Zone.

Mapper.CreateMap<ZoneView, Zone>()
   .ForMember(destination => destination.Title, member => member.Ignore());

You will define this CreateMap once, at application start up. Then map as you have been.

var zone = zonesRepository.Get(zoneView.ZoneId);
Mapper.Map<ZoneView, Zone>(zoneView, zone);

answered Dec 14, 2011 at 14:39

moribvndvs

42.5k12 gold badges138 silver badges152 bronze badges

Sign up to request clarification or add additional context in comments.

12 Comments

Craig Over a year ago

+1 I don't know automapper but this sounds like a better solution then mine. cheers

donRumatta Over a year ago

yes, i create this mapping but without instructions. thank you, i'll try it(=

Craig Over a year ago

Could he also, consider removing the setter from ZoneView.Title as to only accept it through the ZoneView constructor? This way the default model binder wont be able to set the property but he could still display it and that logic becomes a part of the view. Of course the view could not be used elsewhere that allows editing of the Title like in a admin panel though. Just curious what you think?

moribvndvs Over a year ago

He certainly could, but I think that's just jumping through too many hoops unnecessarily. In practice, view models should be very dumb and straight forward, concerned only with specifying the information you want to display or collect, where all the complicated facets of the domain model are flattened or otherwise simplified.

Craig Over a year ago

As I mentioned my thought was he could take it through the constructor but fair enough. To your point I have been using the concept of viewmodels for years now and never put logic business logic in them, was just curious and unfamiliar with using automapper. thanks

|

dotnetstep · Accepted Answer · 2011-12-14 15:10:30Z

0

Most of the time i use Hidden input such values.
And also check at DB level for validation of value with title.

This might not best solution but it works.

answered Dec 14, 2011 at 15:10

dotnetstep

17.5k6 gold badges61 silver badges80 bronze badges

1 Comment

donRumatta Over a year ago

hidden input can be changed by user.

Collectives™ on Stack Overflow

asp.net mvc automapper using

2 Answers 2

12 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

12 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related