ASP.NET MVC3 Best Practices
I have been using MVC3 for about 4 or 5 months and I feel like I am starting to get a good feel for how it works and how to use it.  I have done several searches and it doesn't appear that there are any best practices documents out there.  There are several posts that list different ideas, but nothing pulled all together.

There are several good links on this post:

<http://stackoverflow.com/questions/5492822/mvc-3-with-razor-best-practices>

but this is not complete.  I would like to put compile a list of best practices into a single document.  

**Partial Views**

 - when to use them

 - why to use them

 - how to organize them

The answer to the first two questions is relatively obvious, but I list them to see if there might be some non-obvious answers to them.  The last question deals with what I am struggling right now as I design out my framework.  Some people say to name them with an "_", but I don't like that so much because some of these partial views are requested from ajax and not simply included into another view.  In order to not have to specify the view name in the controller everytime, I have to name the action with an "_" and that doesn't seem right.

I am also interested in how to organize them in the directory hierarchy.  Do you place all your partial views in the Shared folder just because two different controllers may use them?  Even if they would logically be grouped with views of a specific controller?  What if there is an action for the partial view?

**AJAX**

 - single page application design?

 - how to manage/organize javascript

 - If javascript files are included in html loaded via ajax or otherwise loaded via a javascript call, how do you debug it?  Firebug seems to have stripped out all of the formatting.

ASP.NET MVC3 Best Practices
===

I have been using MVC3 for about 4 or 5 months and I feel like I am starting to get a good feel for how it works and how to use it.  I have done several searches and it doesn't appear that there are any best practices documents out there.  There are several posts that list different ideas, but nothing pulled all together.

There are several good links on this post:

<http://stackoverflow.com/questions/5492822/mvc-3-with-razor-best-practices>

but this is not complete.  I would like to put compile a list of best practices into a single document.  

**Partial Views**

 - when to use them

 - why to use them

 - how to organize them

The answer to the first two questions is relatively obvious, but I list them to see if there might be some non-obvious answers to them.  The last question deals with what I am struggling right now as I design out my framework.  Some people say to name them with an "_", but I don't like that so much because some of these partial views are requested from ajax and not simply included into another view.  In order to not have to specify the view name in the controller everytime, I have to name the action with an "_" and that doesn't seem right.

I am also interested in how to organize them in the directory hierarchy.  Do you place all your partial views in the Shared folder just because two different controllers may use them?  Even if they would logically be grouped with views of a specific controller?  What if there is an action for the partial view?

**AJAX**

 - single page application design?

 - how to manage/organize javascript

 - If javascript files are included in html loaded via ajax or otherwise loaded via a javascript call, how do you debug it?  Firebug seems to have stripped out all of the formatting.
