For our ASP.NET Web Application using MVC 5, we are using the built-in ASP.NET Identities system. By default this generates a bunch of useful tables for us, including AspNetUsers. Our Entity Framework model which we've created includes entities which need to use the AspNetUsers.Id column as a foreign key constraint.
It doesn't appear to be possible to create a foreign key to a table not included in our Entity Framework Data Model, but never the less I need to do something to make this foreign key constraint possible, without screwing up the default Identities API.
One idea I had was to create like a "UserProxies" entity in our data model. Then whenever a new User is created and added to AspNetUsers, he/she is also added to our UserProxies table. That way we have a "copy" of the AspNetUsers data in our data model, and can confidently make reference to the UserProxies.Id column and know that it matches up to an AspNetUsers.Id.
This kind of sucks though because it's just duplicating data.
The other idea I had was, just ignore the foreign key constraint and always trust that the relationship is valid. This also sucks (but may be acceptable for what we're doing if there is no solution that doesn't involve re-inventing the wheel).
