There are cases where you want to limit/restrict  the properties of a model that is submitted to the server.

Model class :

[Bind(Exclude="Rid")] ---- Rid properties is excluded from model.

public class ReviewModel

{
public int Rid { get; set; } -- AutoGenerated ,User need not submit it
public String RName { get; set; }
public String RLocation { get; set; }
public int Rating { get; set; }
}

In the above example,Rid is Auto generated and user need not submit it when posted from View. Rid is excluded by using Bind attribute annotation. 

 

 

In layout Pages,renders the content of named Section.

RenderSection("footer",false) ---If set to false,then view need not have a section

The above code expects the Section “footer” to be used and its mandatory,so typically view must have a section named footer.

{
    Layout = ~/Views/Shared/_Layout.cshtml;
}
section footer
{
This is sample footer
}

Working principle of RenderSection :

Render Body : In layout pages, renders the portion of a content page that is not within a named section.

Working Principle of Render Body :

Layouts are like master pages which holds common structure [Example : Header/Footer] that has to be shared across multiple views.

Components of Layouts include :

1.RenderSection

2.RenderBody.

 

 

We can implement Custom Error Handling attribute by implementing ActionFilterAttribute.It has Four methods OnActionExecuted,OnActionExecuting,OnResultExecuted,OnResultExecuting methods which would be overridden in custom class.

class LogAttribute : ActionFilterAttribute
{
public override void OnActionExecuted(ActionExecutedContext filterContext)
{
base.OnActionExecuted(filterContext);
}

public override void OnActionExecuting(ActionExecutingContext filterContext)
{
base.OnActionExecuting(filterContext);
}

public override void OnResultExecuted(ResultExecutedContext filterContext)
{
base.OnResultExecuted(filterContext);
}

public override void OnResultExecuting(ResultExecutingContext filterContext)
{
base.OnResultExecuting(filterContext);
}
}

By Default if an exception occurs in action method,it bubbles up to the FilterConfig which holds the  HandleError that is responsible for catching the exception.Framework also provides a View named “Error.cshtml” in shared folder that is responsible to show the exceptions in UI.

public static void RegisterGlobalFilters(GlobalFilterCollection filters)
{
filters.Add(new HandleErrorAttribute());
}

There are cases where we need to apply certain logic before(Ex: Cache an action) or after(Ex:Log an action ) an action method is executed,In such cases Action Filters are useful.The following are the Attributes supported by Action Filters.

ActionName :

You can customize ActionName in a Controller via ActionName Attribute class.

[ActionName("Find")]
public ActionResult Search(MyModel model)
{
return Content("Hello"+model.Name+model.id);
}

In the Above Method we can only reach the Search Action from Controller via an Action Name Find and not by Search.

The Action Method should Returns one of the following type

We can define parameters that has to be passed to Action Methods in MapRouteMethod,

routes.MapRoute(
"Search",
"{controller}/{name}/{id}",
new{ controller = "Search",action ="Cusine", name = "",id=0}
);

In the above example we define two parameters name and id to the action method Cusine. 

To pass complex object we need to pass each property in the URL,this will get mapped to corresponding model in Action Method:

routes.MapRoute(
"Search",
"{controller}/{name}/{id}",
new{ controller = "Search",action ="Cusine", name = "",id=0}
);

---Action Method

public ActionResult Cusine(MyModel model)
{
return Content("Hello"+model.Name+model.id);
}

public class MyModel
{
public String Name { get; set; }
public int id { get; set; }
}