Use of Attribute Routing possible? about contosouniversity HOT 4 CLOSED

No idea, but it might be something with the controller factory?

from contosouniversity.

I'm currently explicitly defining the custom controller factoy, in Global.asax:

ControllerBuilder.Current.SetControllerFactory(typeof(ControllerFactory))

The contents of the factoy are the same as your ContosoUniversity, bar a namespace change:

public class ControllerFactory : DefaultControllerFactory
{
    protected override Type GetControllerType(RequestContext requestContext, string controllerName)
    {
        return typeof(ControllerFactory).Assembly.GetType($"TestApp.Features.{controllerName}.UiController", throwOnError: false, ignoreCase: true);
    }
}

The controllerName argument passed to the factory is just "Ui".

from contosouniversity.

After doing some investigation, I've got attribute routing working by doing the following:

• Removing the ControllerFactory and its registration
• Removing the convention-based routing declarations

One caveat is that naming your controllers the same, e.g. UiController, won't work, as MVC tries to find views like /Features/Ui/{ViewName}.cshtml; I've named my controllers as {FeatureName}Controller.cs and this works, as the feature folder can be inferred from the controller name. If anyone knows of workaround to this, like a controller name attribute of sorts, I'd be interested!

from contosouniversity.

Well, there's a lot of assumptions built into attribute routing. Honestly
wasn't sure if UiController was a good idea in the first place :)

On Tue, Apr 12, 2016 at 2:24 AM, James Harling [email protected]
wrote:

After doing some investigation, I've got attribute routing working by
doing the following:

• Removing the ControllerFactory and its registration
• Removing the convention-based routing declarations

One caveat is that naming your controllers the same, e.g. UiController
won't work, as MVC tries to find views like the
/Features/Ui/{ViewName}.cshtml; I've named my controllers as
{FeatureName}Controller.cs and this works, as the feature folder can be
inferred from the controller name. If anyone knows of workaround to this,
like a controller name attribute of sorts, I'd be interested!

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#18 (comment)

from contosouniversity.