I have created the following project structure for my new asp.net mvc project any I was after some feedback as how other people are structuring their projects and if I would imp
I've written a couple of (small) sites and simply stuck with the same structure that NerdDinner had and it seemed to work fine.
I think on smaller projects that's a fine approach so long as you have your seperation of concerns, don't place business logic in the repository(s) etc. The temptation on a smaller project is to blur the lines but MVC tends to punish you a little when you do that. :)
Larger projects may see you implementing a seperate business class project and maybe even data translation project etc.