This things which i want.

As a beginner I will have to look around for more examples on how to perform validation on a simple asp.net mvc app. come on....u cud have avoided the shortcut to help us save time.

Thanks anyway :)

Validation should happen there, not in the controller... Right ?

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.Mvc;

namespace incMvcSite.Classes {

public static class HtmlPrefixScopeExtensions {

public static IDisposable BeginHtmlFieldPrefixScope(this HtmlHelper html, string htmlFieldPrefix) {

return new HtmlFieldPrefixScope(html.ViewData.TemplateInfo, htmlFieldPrefix);

}

private class HtmlFieldPrefixScope : IDisposable {

private readonly TemplateInfo templateInfo;

private readonly string previousHtmlFieldPrefix;

public HtmlFieldPrefixScope(TemplateInfo templateInfo, string htmlFieldPrefix) {

this.templateInfo = templateInfo;

previousHtmlFieldPrefix = templateInfo.HtmlFieldPrefix;

templateInfo.HtmlFieldPrefix = htmlFieldPrefix;

}

public void Dispose() {

templateInfo.HtmlFieldPrefix = previousHtmlFieldPrefix;

}

}

}

}

In the Razor (.cshtml) file, I added the following:

@using incMvcSite.Classes

@using(Html.BeginHtmlFieldPrefixScope("Permission")) {

Permission

// The Html.EditorFor's would go here...

}

Notice the using to bring me extension class into scope. That allows the second using line to work.

Now the problem is that when posting back, the object is not updated. In my controller, I used a second parameter to specify my prefix:

TryUpdateModel(modelUser.Permission, "Permission");

This added the prefix to all field in the HTML, and the TryUpdateModel loaded the object with prefixed control names. Now you can properly namespace your controls for embedded edit lists, and for partial views of models with the same property names.

Shawn Zernik

Internetwork Consulting

www.internetworkconsulting.net