title: Best practices regarding locations for ASP.NET MVC models
body: <p>Are there any best practices that cover the places that ASP.NET MVC models should be defined?</p>
  
  <p>A new ASP.NET MVC project has a nice neat Models folder for them to go in, but in a production environment they can come from other places:</p>
  
  <ul>
  <li>Third party class libraries</li>
  <li>WCF services</li>
  </ul>
  
  <p>Is it acceptable for a strongly-typed view to use a class defined in such a location?</p>