title: Naming conventions - One rule for Controllers, no rules for Models and Views
body: <p>In ASP.NET MVC controllers exist in a folder called Controllers. Their names must end <code>Controller</code> otherwise things just don't work (you get an HTTP 404 error).</p>
  
  <p>However, Model names don't have to end <code>Model</code> and View names don't have to end with <code>View</code>.</p>
  
  <p>This seems inconsistent...why (from an MVC or design standpoint) do controller names have to end <code>Controller</code>?</p>
  
  <p>Do other MVC frameworks have this requirement?</p>
  
  <h2>Edit</h2>
  
  <p>Since this appears to be the convention I am not advocating going against it (see <a href="http://en.wikipedia.org/wiki/Convention_over_Configuration" rel="nofollow noreferrer">Convention over Configuration</a>!), but I want to understand the reasons behind it.</p>