I have made a question few days ago on how to make a many-to-many relationship between the Asp.Net Identity table and my custom table.
Here the thread with the answer: Q&A
Someone told me that from an architectural point of view it's best to handle user information and business data separately. I quote: "That said from an architectural point of view it seems best to handle user information and business data separately, I would perhaps rather aggregate both behind a facade but keep them separate under the scene"
In the answer someone gave me, which is a solution, he told me to use the ApplicationDbContext to work with the tables, etc.
Now going back to what the other person said me, I want to keep my hands away from the ApplicationDbContext, which is the Identity context, and work only with my own context.
Can someone give me a workaround how to archive that? Thank you!