We do not yet support constructor injection within the business controller class (we need to wait until version 10 because implementing that will be a breaking change, affecting the lifetime of the created instances).

We do support constructor injection for Web API controllers.

In this example scenario, are you using a Web API controller (i.e. <code>DnnApiController</code>) as the business controller class? I would recommend separating those two ideas if you can into two separate classes.

For now, if you need to access something from the dependency injection container and the framework doesn't provide easy access to it, you have two options. The first option is that you can continue to use the deprecated API until a newer API is available (i.e. use <code>Globals.NavigateURL</code> for now). The second option is that, if you are using your API in a context where you are guaranteed to have an HTTP context (e.g. not in a scheduled task, not in search indexing, not in import/export, etc.), you can access the dependency injection scope from the HTTP context (see example code). (And, I suppose, a third option would be to create your own class that  implements the <code>INavigationManager</code> interface, though ultimately you'll probably want to fall back to <code>Globals.NavigateURL</code> for the implementation).