When I try and start two apps on different url's, I get problems with attribute routing middleware. If I have two similar routes in seperate apps but with different http methods web.api seems find only one of the methods.
Microsoft.Owin.Hosting.WebApp.Start<Admin.Startup>("http://localhost:1000");
Microsoft.Owin.Hosting.WebApp.Start<Startup>("http://localhost:1001");
How can I isolate both apps so that attribute routing don't conflict?
Based on your last comment, an example below to filter out the assemblies:
I had the exact same issue and @KiranChalla's answer got me going down the right path (thanks!). The problem was indeed with the assembly scanning going deeper than I wanted it to. For me I always wanted the scan to only include the assembly where the "current"
Startup
is defined, as that is the Web API project where all relevant controllers live. I created a resolver that always returns just one assembly:And told it which assembly ("this" one) when registering it in each
Startup
: