Asp.Net Core: late registering OData EDM + Controllers after build/run

[skysgh]

Hi,
We embarked some time ago on using AspNetCore for an API server, expecting to find an answer to the following problem. But haven't, and now stakeholders are jumpy and want proof before they pull us onto another platform.

Specifically, it is required to support 3rd party plugins.
Each plugin may contain an unknown small set of Controllers and ODataControllers.

The default behaviour of Asp.Net Core is to register all routes, including EDMs are startup.
Although fine for base system services, this is not applicable for 3rd party plugins not known at startup that may be uploaded at runtime.

What we are asking help with is enough information to develop the following to demonstrate to stakeholders that AspNetCore can be used:

Specifically:

• One solution, one project
• Two OData Controllers
• At startup,
• register one Convention based EDM Model with one service root (eg: 'api/odata/Base'),
• pointing to only one of the OData Controllers
• such that when invoked it
• registers the second EDM model with another service root (eg: 'api/odata/ModuleA'),
• and registers the route to the second OData controller
• proving that models and controllers can be registered late (and therefore api plugins is possible on Asp.Net Core).

I am sure that it can be done...just need help getting there.

Thank you for your help!

(I'd attach what we've attempted...but since it's now just a jumble of hell and failed routes, it probably won't add any value.)