How to a separate ASP.Net Core Application using same Database

Question

I have an existing ASP.Net Core Web API and now I want to create the admin module as a separate ASP.Net Core application but sharing the same database.

My problem now is how to handle my DBContext in the new solution especially because of the the following line containing the ApplicationUser model

public class ApplicationDbContext : IdentityDbContext<ApplicationUser>

and also the other model classes which exist in the existing solution from where I need to create my DBSet entitie sets to enable me query the database.

I wish to have the admin module to be a completely separate application hosted on a different domain/server but having access to the same database so that the admin can manage the database table entries from the admin solution.

I don't want it to be a separate project on the same solution. Rather I want it to be a completely separate solution/application which can be hosted independently.

I will appreciate any guide to achieving this if it is possible with ASP.Net Core.

I am using ASP.Net Core 5 with Entity Framework Core but I can migrate to version 6 if that offers a solution.

I would start by completely separating ApplicationDbContext and IdentityDbContext. But we can only give opinions and suggestions here. — Gert Arnold
– Gert Arnold, Commented Jan 16, 2022 at 18:54
@GertArnold your opinion and suggestions are highly welcome. Please go ahead and explain how to go about it — Josh
– Josh, Commented Jan 16, 2022 at 20:22

Felix · Accepted Answer · 2022-01-16 17:24:32Z

1

You need to create a model as a separate (third) project, build a nuget of that Model project and include it in both. There are some small challenges, since you are going to run migrations on this standalone project - but nothing that cannot be overcome

It's very straightforward (and possible since ASP.NET Core 1).

answered Jan 16, 2022 at 17:24

Felix

10.2k10 gold badges64 silver badges105 bronze badges

Sign up to request clarification or add additional context in comments.

10 Comments

Josh Over a year ago

Can the models be a class library instead of a nugget? Or could you explain more why it has to be a nugget

Felix Over a year ago

First, it's nuget, not nugget. Second - and more important, it is class library. nuget is the easier way to package class library, and include in other projects. But if you want more pain - sure, you can just fight unpackaged DLLs

Josh Over a year ago

Thank you. I will give it a shot and revert

Josh Over a year ago

Do you mean that the DBContext and the models would be the make-up of the 3rd standalone application?

Felix Over a year ago

@Josh - yes, exactly

|

Masoud Sharifi · Accepted Answer · 2022-01-16 17:43:50Z

0

You can have multiple contexts for single database. It can be useful for example if your database contains multiple database schemas and you want to handle each of them as separate self contained area.

Read the link below

https://www.tutorialspoint.com/entity_framework/entity_framework_multiple_dbcontext.htm

answered Jan 16, 2022 at 17:43

Masoud Sharifi

943 bronze badges

1 Comment

Felix Over a year ago

This has nothing to do with original question - but hey, it may help somebody else

Collectives™ on Stack Overflow

How to a separate ASP.Net Core Application using same Database

2 Answers 2

10 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

10 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related