title: .NET class prefix and postfix naming conventions
body: <p>Developer teams usually have some class naming conventions based on class functionality and roles it plays in patterns. For example, we use the following <strong>postfixes</strong>: </p>
  
  <ul>
  <li><strong>Info</strong> for data structure classes (only public properties, no methods, such as business entities). </li>
  <li><strong>Helper</strong> for classes with common functionality used all over the project (StringHelper, FormatHelper, ImageHelper)</li>
  <li><strong>Controller</strong> for MVC-controllers </li>
  <li><strong>Repository</strong> for DAL classes that contains operations grouped by entity they dedicated to (PersonRepository, OrderRepository)</li>
  <li><strong>Manager</strong> for business logic classes</li>
  </ul>
  
  <p>Etc.</p>
  
  <p>What are the naming conventions for postfixes/prefixes your team uses?</p>