title: Structuring of Asp.net MVC controller folders for better cohesion
body: <p>When building complex applications the controllers can start to get unwieldy and very large, which may mean that you split them out into separate controllers. This may not be suitable as it will be reflected in the users experience. Ie. They will see the controller name in the URI.</p>
  
  <p>For example: The default project that ships with MVC has an AccountController,  that has actions for login, logoff, register etc.. which seems to violate the <a href="http://en.wikipedia.org/wiki/Single_responsibility_principle" rel="noreferrer">Single Responsibility Principle.</a> </p>
  
  <p>So the question is how to resolve this problem and separate out the concerns? An initial response could be just to create separate controllers. Ie.</p>
  
  <pre><code>AccountLoginController
  
  AccountRegisterController
  </code></pre>
  
  <p>But this would not be a great experience from a customers point of view as it would effect the URI when requesting the resource.</p>
  
  <p>A solution could be to have separate folders for each controller which contains separate class files for the action, each one with a single responsibility like so.</p>
  
  <pre><code>Controllers (folder)
      Account  (folder)
          Register.cs
          Login.cs
          Logout.cs
      AnotherController (folder)
          Actionfile.cs
          Actionfile.cs
  </code></pre>
  
  <p>The above would separate out the functionality and be <a href="http://en.wikipedia.org/wiki/Cohesion_%28computer_science%29" rel="noreferrer">highly cohesive</a>.</p>
  
  <p>So, this is a long explanation, but my questions are..</p>
  
  <ul>
  <li><p>Has anyone implemented this before?</p></li>
  <li><p>If so how do you go about it?</p></li>
  <li><p>What are your thoughts regarding this pattern?</p></li>
  </ul>