title: add new SQL Table to Identity 2.0 data context
body: <p>I've been building an ASP.NET MVC5 Web App with Identity 2.0 hosted in Azure (using <a href="http://www.codeproject.com/Articles/762428/ASP-NET-MVC-and-Identity-Understanding-the-Basics" rel="nofollow noreferrer">this article</a> and <a href="http://www.codeproject.com/Articles/682113/Extending-Identity-Accounts-and-Implementing-Rol" rel="nofollow noreferrer">this article</a> for guidance on implementing Identity 2.0), and have encountered an issue that I'm hoping someone can help with.</p>
  
  <p>My issue ultimately stems from the need to add additional SQL Tables, and not knowing the proper way to handle this from a data context perspective. With Identity 2.0 fully working and hosted in my web app's Azure SQL, the next goal was to create a new custom table for storing some additional data. Creating the new class in my Model, adding scaffolding and creating a controller were all easy enough, but what I can't figure out is the data context. </p>
  
  <p>What I had originally done (which seemed to be working for awhile, until trying to enable Code-First Migrations and inadvertently dropping my Identity 2.0 tables) was create a second data context inheriting from DbContext, as such (please ignore the red squiggles under "WepApp", changed this to something generic for purpose of sharing):</p>
  
  <p><img src="https://i.stack.imgur.com/8luqC.jpg" alt="Please ignore red squiggles under &quot;WebApp&quot;. Changed this to something generic for purpose of sharing."></p>
  
  <p>I then used this new data context in the Controller for this class, as shown below:</p>
  
  <p><img src="https://i.stack.imgur.com/my6iD.jpg" alt="enter image description here"></p>
  
  <p>While this worked to get the job done at first, when trying to update this new table by adding additional columns I inadvertently dropped my Identity 2.0 tables, and now get "multiple data context" errors whenever I try to do any migration action, preventing me from recreating them. My suspicion, although I'm far from certain, is that I should have integrated my new table into the same data context as the Identity 2.0 tables, since they are different tables in the same database. </p>
  
  <p>Can anyone offer any advice for properly adding additional tables to the database housing an Identity 2.0 system? In particular, how should this be handled from a data context perspective? I'm somewhat desperate right now as I've completely lost my Identity 2.0 backend tables, and am struggling to get them recreated. Thanks.</p>