Ever since I started discovering the MVC world I decided to completely forget Web Forms and actually adopt asp.net MVC as my web programming framework of choice. What's great about it is that you have complete control over the generated html output and absolute separation of business logic, presentation layer and model. It's all about convention over configuration! This is one of the reasons why I decided to learn Ruby on Rails some time ago. It is clear that the ASP.NET MVC .NET Framework 3.5 SP1 release was somewhat influenced by Rails.
One of the great things about ASP.NET MVC is model binding. K. Scott Allen wrote a great blog post with tips on binding. Basically, it collects your request data and fills up your view model with the incoming data.
There is a search pattern that the DefaultModelBinder uses to look for the data in the request. Basically you need to name your form elements with the same name of your model properties. For example:
1. The view model:
1: public class NewsModuleViewModel
2: {
3: [ScaffoldColumn(false)]
4: public int ID { get; set; }
5:
6: [DisplayName("News Date")]
7: [DisplayFormat(DataFormatString = "d", ApplyFormatInEditMode = true)]
8: [Required(ErrorMessage = "Por favor selecione uma data")]
9: public DateTime? Date { get; set; }
10:
11: [DisplayName("Title")]
12: [Required(ErrorMessage = "Por favor digite um título")]
13: public string Title { get; set; }
14:
15: [DisplayName("Resume")]
16: public string Resume { get; set; }
17:
18: [DisplayName("My Text")]
19: [UIHint("HtmlText")]
20: [Required(ErrorMessage = "Por favor digite um texto para a notícia")]
21: public string Text { get; set; }
22:
23: [DisplayName("Image")]
24: [UIHint("DbImage", null, "AspectRatio", 1.0)]
25: public string ImagePath { get; set; }
26: }
2. The form:
1: <form action="/uac/NewsModule/Edit/12" enctype="multipart/form-data" method="post">
2:
3: <p class="datalist-form">
4: <label for="Date">Date</label>
5: <input type="text" id="Date" name="Date" value="22/1/2010" />
6: </p>
7: <p class="datalist-form">
8: <label for="Title">Title</label>
9: <input class="text-box single-line" id="Title" name="Title" type="text" />
10: </p>
11: <p class="datalist-form">
12: <label for="Resume">Resume</label>
13: <input class="text-box single-line" id="Resume" name="Resume" type="text" />
14: </p>
(I've reduced the HTML markup snippet for the sake of simplicity).
Please note that the input field name properties match the view model property names. The DefaultModelBinder will look for these names when doing the data binding!
You can even bind complex objects like lists, for example, but, in this case, you'll have to name your input fields according to the element index on the list! Eg.:
1: <input type="text" name="ImageList[0].FileName" size="44" />
It is really straightforward once you get used to it. Just always make sure to create a ViewModel class for you, instead of using the data classes directly (eg.: with LINQ to SQL).
If you need to bind uploaded files as well, it gets a bit more complicated. The best solution I've found so far was not to bind file input control and later retrieve the uploaded file in the controller action from the Request.Files collection.
