title: Should I separate my application context from ApplicationDbContext used for identity?
body: <p>In Visual-Studio 2013, when creating an ASP.NET project, it generates a file <em>IdentityModels.cs</em> that contains a class <code>ApplicationDbContext</code>, that inherits from <code>IdentityDbContext&lt;ApplicationUser&gt;</code>, which eventually inherits from <code>DbContext</code>.</p>
  
  <p>Should I keep this context only for account-related entities, and created a separate context for all the other entities in the application or should I mix it.</p>
  
  <p>Any security issue or reason not to include all the entities of my entire application in one context?</p>