title: How to structure ASP.NET MVC application using per-feature organization instead of per-artifact?
body: <p>I would like to know how can I do to structure a web application using one folder per feature (Customers, Orders)  instead of one folder per artifact type (Controllers, Views); this seems to be a much better way to organize large projects with lots of features, but I can't find any information about it.</p>
  
  <p>I don't think that using Areas would be a solution because using one Area per-feature would require creating lots of nested folders.</p>
  
  <p>I think that what I want to do should be possible by customizing a IViewEngine implementation, but I'm not sure about that.</p>
  
  <p>Has anyone tried to do this?</p>