title: Is there a best or recommended practice for naming Entity Framework migrations?
body: <p>When using Entity Framework code first migrations is there a best practice for choosing a name for each migration?  For example each name might contain a version number or the change(s) made to the model or both.</p>
  
  <pre><code>Add-Migration Added Manager.Employees
  Add-Migration Add_Employee_ManagerId
  Add-Migration version 2
  Add-Migration v2_Add_Employee_ManagerId
  </code></pre>
  
  <p>Any tips for selecting a good naming strategy for a project with multiple developers and many migrations?</p>
  
  <p>I found a <a href="https://stackoverflow.com/questions/26712297/naming-conventions-for-code-first-migrations">similar question</a> but no answers.</p>