.NET Core Identity. Use one context or two?
问题 I am struggling with a basic problem. Keep my ASP.NET Core Identity context separate from my business context or combine the two. Philosophically, it seems good to keep them separate. If I want to upgrade .NET Core at some point in the future, I have fewer issues if my identity context is separate. Practically, it seems like a good idea to combine them. Otherwise, I am creating another user table or doing some weird workarounds to get user information from navigation properties. How do you