arrow_back An ASP.NET web service and its admin panel (a Windows application) are two different applications, or can they fit into one?

Question

There is the task described in the title.
There must be a service that sticks out (albeit within the same company) and this service needs an admin interface (adding/removing users, searching logs, disabling/enabling this service, etc.).

I haven't worked with ASP.NET before, but now I tried to write a simple service and then, within the same application, make a small GUI for it. It worked, but it was like a (not) big perversion.

It seems to me that there should be two applications, the web service itself and its admin panel.
There is only one question, is it possible (and how) to run a web service application from the admin area?
Just calling Main of the web service project didn't work (logically). Is there any way to run a web service other than just running its exe file?

Comments

It makes more sense to do it all in one application.
You deploy a single web application and within it, ordinary users have access to standard functionality, while admins have access to advanced functionality.

If you will use a Windows application, the administrators will have to constantly send the current version of the program, if any changes in the functionality of the admin panel.

About running a web application. This is quite a costly operation. Usually you deploy a web service and it always works. And in the application itself, you can implement login blocking for normal users, through the admin panel.

If, of course, the task is to stop the site in Win Server in IIS, that is example . In this case, you can't do without a second application.

Answer 1

You are trying to implement a three-link (in your case four-link, which really should be three-link xDD) architecture.

Don't try to cram what you can't cram in. Make a core service that makes everything else a client. You'll be very happy. It doesn't really matter what it'll be based on or how it's implemented. You can at least use Java's Spring - everything is compatible on the protocol level.

Comments

That would be true if the task were not exactly as described in the question. These requirements are not made by me, and, in this case, I cannot deviate from them.

Answer 2

Why would you need a Windows application to administer a web service when you have a browser, or even several browsers, on the Windows? They are also windows programs. And very GUI too.
Just write a web service, a user muzzle and an admin muzzle.

And normally the service on the user should be separated from the administrative part, i.e. not carry a byte of administrative code like this:

Comments

That would be true if the task were not exactly as described in the question. These requirements are not made by me, and, in this case, I cannot deviate from them.