Speaking of NerdDinner, Scott asked me to use it to create an AutoMapper example. 
AutoMapper, the brainchild of Jimmy Bogard, is an object-to-object mapper. What that means is up to you – but we’ll use it here to map from the domain model to a view model. The view model is an object heirarchy that represents the screen. It’s as dumb as possible, just like the view.
We get a lot of nice things out of it and it helps us go faster. You can read more about it AutoMapper from Jimmy or at the website on Codeplex.
For starters, NerdDinner isn’t the best scenario in which to apply AutoMapper. NerdDinner is very small so there’s not much reuse to harvest. For example, if you format dates the same way a million times you can use AutoMapper to only write that formatting code once. In a small application you may format dates two ways and only use the resulting text in two views. It doesn’t make a lot of sense to extract a class just for that – it will seem like a lot of overhead.
Also NerdDinner doesn’t have a rich domain model – there’s just not that much to do. So the AutoMapper feature of flattening complex hierarchies can’t be appreciated.
I posted the result of this quick and dirty spike as a sample project – hopefully this will help you get started looking at it.
First, I copypasted a class to bootstrap AutoMapper:
namespace NerdDinner.Helpers.AutoMapper
{
public class AutoMapperConfiguration
{
public static void Configure()
{
Mapper.Initialize(x => x.AddProfile<ViewModelProfile>());
}
}
}
.. which will be called when the application starts:
void Application_Start()
{
AutoMapperConfiguration.Configure();
RegisterRoutes(RouteTable.Routes);
ViewEngines.Engines.Clear();
ViewEngines.Engines.Add(new MobileCapableWebFormViewEngine());
}
I copypasted another class that will check the mapping configuration for errors, providing fast feedback should I make a mistake.
[TestClass]
public class AutoMapperConfigurationTester
{
[TestMethod]
public void Should_map_dtos()
{
AutoMapperConfiguration.Configure();
Mapper.AssertConfigurationIsValid();
}
}
Now I’m ready to begin creating the view model and configuring AutoMapper.
To design a view model, start with the screen. What’s displayed will be represented in the model. Again: the view model is an object hierarchy that represents the user interface. I picked the Dinner Details screen, by the way.
The current model being used by the view was the Dinner entity itself. There was a lot of formatting in the view and a lot of duplication.
Almost every property was surrounded by code that would HtmlEncode it (it will be nice to have AutoMapper do this for us):
<%= Html.Encode(Model.Title) %>
And there is a lot of formatting to do:
<abbr class="dtstart" title="<%= Model.EventDate.ToString("s") %>">
<%= Model.EventDate.ToString("MMM dd, yyyy") %>
<strong>@</strong>
<%= Model.EventDate.ToShortTimeString() %>
</abbr>
Imagine a project with 300 screens and a team of analysts and you can imagine that specifying this formatting over and over again in requirements documents and planning would become tedious. Not to mention coding it. It’d be easier to just say: “Format this date in the standard way.” You can also imagine the security implications of forgetting to encode even one value.
In converting these screens to use a view model instead of the domain model I didn’t want to change existing functionality. So I took this:
<%@ Page Language="C#" Inherits="System.Web.Mvc.ViewPage<NerdDinner.Models.Dinner>"
and changed it to this:
<%@ Page Language="C#" Inherits="System.Web.Mvc.ViewPage<DinnerDetailsViewModel>"
See what I did there? I just changed the type of the Model property to a new DinnerDetailsViewModel type.
The view will receive a view model mapped from the domain model when I apply a special action filter to the controller action:
[AutoMap(typeof(Dinner), typeof(DinnerDetailsViewModel))]
The code’s in the sample, straight from Jimmy’s post.
I started out with DinnerDetailsViewModel being an empty class definition and used Resharper to generate each property as I encountered it. I removed the formatting and the ubiquitous encoding from the parameters, turning this:
<div id="dinnerDiv" class="vevent">
<h2 class="summary"><%= Html.Encode(Model.Title) %></h2>
<p>
<a href="http://feeds.technorati.com/events/<%= Url.AbsoluteAction("Details", new { id = Model.DinnerID }) %>">
Add event to your calendar (iCal)
</a>
</p>
<p>
<strong>When:</strong>
<abbr class="dtstart" title="<%= Model.EventDate.ToString("s") %>">
<%= Model.EventDate.ToString("MMM dd, yyyy") %>
<strong>@</strong>
<%= Model.EventDate.ToShortTimeString() %>
</abbr>
into this:
<h2 class="summary"><%= Model.Title %></h2>
<p>
<a href="http://feeds.technorati.com/events/<%= Url.AbsoluteAction("Details", new { id = Model.DinnerID }) %>">
Add event to your calendar (iCal)
</a>
</p>
<p>
<strong>When:</strong>
<%= Model.EventDate %>
</p>
I had to write a formatter to replace the custom formatting performed by the view.
public class AttendeeNameFormatter : BaseFormatter<string>
{
protected override string FormatValueCore(string value)
{
return value.Replace("@", " at ");
}
}
See how testable that is; small and reusable?
I also moved some methods that were previously being called from the view directly into the domain model which AutoMapper will evaluate at runtime.
Before:
<p id="whoscoming">
<strong>Who's Coming:</strong>
<%if (Model.RSVPs.Count == 0){%>
No one has registered.
<% } %>
</p>
After:
<p id="whoscoming">
<strong>Who's Coming:</strong>
<%if (Model.IsNobodyRegistered){%>
No one has registered.
<% } %>
</p>
The view model for this screen ends up looking like this:
public class DinnerDetailsViewModel
{
public string Address { get; set; }
public string Title { get; set; }
public string DinnerID { get; set; }
public string EventDate { get; set; }
public string Country { get; set; }
public string Latitude { get; set; }
public string Longitude { get; set; }
public string Description { get; set; }
public string HostedBy { get; set; }
public string ContactPhone { get; set; }
public bool IsAnyoneRegistered { get; set; }
public bool IsNobodyRegistered { get; set; }
public bool IsCurrentUserRegistered { get; set; }
public bool IsCurrentUserHosting { get; set; }
public List<RsvpViewModel> RSVPs { get; set; }
public class RsvpViewModel
{
public string AttendeeName { get; set; }
}
}
The really key part is the AutoMapper configuration profile. You can group configurations with profiles. Maybe in one profile you format dates in one way, in another profile you format dates in another way. I’m just using one profile here.
public class ViewModelProfile : Profile
{
protected override string ProfileName
{
get { return "ViewModel"; }
}
protected override void Configure()
{
AddFormatter<HtmlEncoderFormatter>();
ForSourceType<DateTime>().AddFormatter<StandardDateFormatter>();
CreateMap<Dinner, DinnerDetailsViewModel>()
.ForMember(x => x.IsCurrentUserRegistered, o => o.ResolveUsing<CurrentUserRegisteredResolver>())
.ForMember(x => x.IsCurrentUserHosting, o => o.ResolveUsing<CurrentUserHostingResolver>())
.ForMember(x => x.EventDate, o => o.SkipFormatter<HtmlEncoderFormatter>());
CreateMap<RSVP, DinnerDetailsViewModel.RsvpViewModel>()
.ForMember(x => x.AttendeeName, o => o.AddFormatter<AttendeeNameFormatter>());
}
}
Most properties of the view model are mapped conventionally. The property names match up so AutoMapper knows exactly what do do with them. AutoMapper will do a lot more for you if you’d like it to. This is actually a pretty hefty configuration. In a different scenario it’d be likely that almost everything is mapped conventionally.
Note the first AddFormatter call. That’s instructing AutoMapper to html encode everything. I skip it for a property later. The possibilities here are endless. One cool thing we do in another project is wrap each property in a span that’s given a conventionally named CSS class. In automated UI tests, we can use that class to find the proper element and ensure that the screen is displaying the right thing.
Let me know if you have any questions.
