public void ConfigureServices ( IServiceCollection services ) Īll that remains is to register the hosted service in Startup. The example below adds the assembly that contains TestController (which resides in a different project) as an application part.

The current assembly is added automatically, but you can add additional application parts too. I did some reasearching and found the BetterJoyforCemu and installed both that and cemu itself (I didn't know if it was necessary) but neither strategies worked so I went. So I tried adding P64 to steam using big picture and when I ran the game it wouldnt detect the controller, only the enter key. You can add application parts in ConfigureServices when you configure MVC. Trying to play OoT with Switch Pro Controller. This is the situation I had in the app I described previously - each of the module projects was compiled into a separate Assembly, and then added to the application as application parts. One application part implementation is an AssemblyPart which is an application part associated with an assembly. If you're familiar with Razor Class Libraries, then think of application parts as being the abstraction behind it. Application Parts allow ASP.NET Core to discover controllers, view components, tag helpers, Razor Pages, razor compilation sources, and moreĪpplication Parts allow you to share the same resources (controllers, Razor Pages etc) between multiple apps. What are application parts?Īn Application Part is an abstraction over the resources of an MVC app. The solution I present in this post let me rule out point 3, by listing all the ApplicationParts and controllers the app was aware of. My gut feeling was the problem was either 1 or 3, but I needed a way to check.

The ASP.NET Core app wasn't aware of the controllers in the module at all.

There was a problem with the controllers themselves, meaning they were generating 404s.

There was a routing issue, so requests meant for the controllers were not reaching them.

There were a few possibilities in my mind for what was going wrong: All of the requests to certain modules were returning 404s. One thing that had me stumped for a while was why the controllers from some of the modules didn't seem to be working. But, of course, there were bugs in the conversion process. There was then a 'top level' application that referenced all these modules and served the requests.Īs the whole solution was based on Katana/Owin and used Web API controllers exclusively, it wasn't too hard to convert it to ASP.NET Core. These modules contained everything for that feature: the database code, the domain, and the Web API controllers. The solution had many class library projects, where each project represented a module or vertical slice of the application. Debugging a missing controllerĪ while ago I was converting an ASP.NET application to ASP.NET Core. I then show how you can retrieve the list at runtime for debugging purposes. In this post I describe application parts and how ASP.NET Core uses them to find the controllers in your app.

Project 64 wont detect controller