title: MVC 3 project structure
body: <p>I am trying to find the best way to layout my MVC 3 project. When searching online I came across a suggestion that basically said right click on project and add area. What this did was create an area folder with same controller/view/model structure in the same project. This is not what I want. I want the flexibility of having separate projects. I will keep only the views in the main web project. Everything else in a separate project. </p>
  
  <p>Towards that attempt I created a separate project for my controllers. Now I am stuck with pointing a controller action to a view. In all the online examples it was right click and add view. This being a class library project I don't have that flexibility. <strong>Where am I going wrong?</strong></p>
  
  <p>All examples that I have found including the ones I have gone through on <a href="http://www.asp.net/mvc/tutorials/getting-started-with-aspnet-mvc3">Asp.net</a> basically explain how to create study applications, which is only good for learning purposes. A large commercial application can't possibly have all the views/models/controllers in one project. Or is that the way it is supposed to go in MVC? <strong>I am not sure if doing everything with mouse clicks is also a good idea.</strong> In the webforms world also there were a lot of study-for-beginners applications that used mouse clicks to create basic CRUD applications, but in real commercial projects, we never used those methods. </p>
  
  <p>What are your thoughts, guidance on this?</p>
  
  <p>Thanks for your time...</p>