I want to create a relationship between the user table (s) and the default aspnet tables associated with users.
I use code-first, so for most FK relationships I just did
public ModelName ModelName { get; set; }
In doing so, EF will automatically create FK relationships. Very easy.
Which is confusing the most efficient way to connect to an aspnet user / membership table. Create a new model. Users who act as an interface so that I can implement user user code?
Is there a better way to do this that fits well with EF best practices? I just want to associate a user with a website table / model so that EF can accomplish its task.
source
share