ASP. net mvc best practices 27 +

12 ASP. net mvc Best Practices

M

Domainmodel! = Viewmodel

Use actionfilters for "shared" Data

V

Do never user code-behind

Write HTML each time you can

If there is an IF, write an htmlhelper

Choose your view engine carefully

C

Delete the accountcontroller

Isolate controllers from the outside world

Use an IOC container

Say no to "magic strings"

Build your own "personal conventions"

Pay attention to the verbs

 

ASP. net mvc Best Practices

Use

Use jquery and jquery UI

Use bootstrapper in global. asax

Use action filter to convert to compatible action Methods Parameters

Use updatemodel carefully

Use PRG pattern for data modification

Do not

Do not make any hard dependency on the Di container, use common service locator

Do not put your JavaScript codes in your view

Avoid viewdata, use viewdata. Model

Do not make any hard dependency on the Di container, use common service locator

Controller will not contain any domain Logic

Decorate

Decorate your most frequent action methods with outputcache attribute

Decorate your action methods with proper acceptverbs attribute

Decorate your most frequent action methods with outputcache attribute

Decorate your action methods with proper acceptverbs attribute

Create

Create new actionresult if required

Create extension methods of urlhelper to generate Your URL from route

Create layer super type for your viewmodel and use action filter to populate common parts.

Create Extension Method of urlhelper to map your JavaScript, stylesheet and image folder

Htmlhelper Extension

Split your view into multiple viewusercontrol

Tips

Routing consideration

Encode

Action filter location

Keep your controller free from httpcontext and its tail

Original article address:

Http://weblogs.asp.net/rashid/archive/2009/04/01/asp-net-mvc-best-practices-part-1.aspx
Http://codeclimber.net.nz/archive/2009/10/27/12-asp.net-mvc-best-practices.aspx