How to design the architecture of an ASP.NET MVC application in this case?

Question

ASP.NET

Suppose there is a solution in it, the asp.net mvc project itself, well, in addition to it, there are many projects of the classlibrary type for the repository, for tools (of the webextentions type), etc. in the solution.
The task is to enable another project (several projects), on schedule, independently (asynchronously??) from the main asp.net mvc project, to connect to the database and make changes there.
How would you design such a solution?
Thanks in advance !

Answer 1

I did not quite understand the essence of the question.
If working with data in your project is moved to a separate library and the MVC application uses this library, nothing prevents you from creating another application (console or service) next to MVC that will work independently using the same libraries. The console application can be launched through the OS scheduler, if the service is - here you decide when and what to do.
If the code for working with the base (contexts, models, or at least ADO.NET) is in MVC, then it is worth refactoring.
For communication between MVC and non-MVC applications, you can make a special endpoint (in the case of console -> MVC), or an event queue (for console <-> MVC), but this is if necessary.