3

I have created windows forms application in .netcore 3.1 , that host two WEB Api services, using WebHostBuilder from the framework dependence of AspNetCore 3.1. (one on port 5000, one on 5001).

I have also created two ApiControllers, with annotations:

[Route("api/[controller]")] [ApiController]

And the second one:

[Route("api2/[controller]")] [ApiController]

In both Startup classes, I am setting:

services.AddControllers();

and later:

endpoints.MapControllers()

And it works like a charm.

Now I want to the first controller to be accessible only to port 5000, and the second only to 5001. And the runtime is adding both of them, to the both WEB Api.

So for example:

First Api (at port 5000)

...:5000/api/ - works!

...:5000/api2/ - 404!

Second Api (at port 5001)

...:5001/api/ - 404!

...:5001/api2/ - works!

Is there a way to register specific controller to specific WEB Api, instead of adding everything that is inside your project?

For example, add only controllers, that start with route "api/" or any in specific namespace, or ...any way whatsoever...

H.A.H.
  • 2,104
  • 1
  • 8
  • 21
  • 1
    Have you tried to create a custom middleware to capture incoming requests and return specific response based on request path? – Fei Han Jul 06 '20 at 08:59
  • Yes, I know about this workaround. I have tried app.Use( async (context, next) => from IApplicationBuilder. And then use the Request of the context to handle it. And it works... But I would like to just skip adding the controller, not just handle every single request and stringsearch, because there is no much point in using Web API and patching it like that. – H.A.H. Jul 06 '20 at 09:22

1 Answers1

2

So I have spend the weekend going through every single answer that is even remotely connected to my case.

So basically what you have to do is ConfigureApplicationPartManager like that:

services.AddControllers().ConfigureApplicationPartManager( manager = >...

And then you can add/remove parts. (if you want to remove assembly for example)

And override the IsController method of ControllerFeatureProvider. (So you basically tell what is controller and what not.)

This way you can host two separate WEB Api, each with its own set of controllers. I decided to make them in two separate namespaces, in two separate folders, and manage them like that in my project.

From the millions of words I have read, I found those two answers extremely useful: https://stackoverflow.com/a/48787571/6643940

https://stackoverflow.com/a/37647605/6643940

I hope this helps someone in the future.

H.A.H.
  • 2,104
  • 1
  • 8
  • 21