Area attribute routing about attributerouting HOT 5 CLOSED

Is there any reason why you did not use the RouteArea attribute on the
controller? That's where area support comes in.

On Sep 7, 2011, at 6:37 AM, jansaris
[email protected]
wrote:

Hi,

I have found an issue in the area routing.
If you add a controller to the area routing which starts with the same name as the area, the routing goes wrong.

So in your demo project you have an area called Admin.
I've added the following controller:

public class AdministratorController : AdminControllerBase
{
[GET("Administrators")]
public ActionResult Index()
{
return View();
}
}

I've added the corresponding View.

I assume that the following route will be added to the routing table:
http://localhost/Admin/Administrators
But instead the following route is added to the routing table:
http://localhost/Administrators

Could you please look in to this issue?

Thanks
Jan Saris

Reply to this email directly or view it on GitHub:
#15

from attributerouting.

In my example I've used this git-hub example application (AttributeRouting.Web.csproj).
If you look in the example code, you see that the baseclass: AdminControllerBase contains the RouteArea attribute.

[RouteArea("Admin")]
public class AdminControllerBase : ControllerBase
{
}

And my code uses this baseclass:

public class AdministratorController : AdminControllerBase
{
[GET("Administrators")]
public ActionResult Index()
{
return View();
}
}

But if I put the RouteArea attribute directly on this class (without use of the base-class) the issue also occurs.

from attributerouting.

Cool. Thanks for the follow up. I'll check it out.

On Sep 8, 2011, at 3:11 AM, jansaris wrote:

In my example I've used this git-hub example application (AttributeRouting.Web.csproj).
If you look in the example code, you see that the baseclass: AdminControllerBase contains the RouteArea attribute.

[RouteArea("Admin")]
public class AdminControllerBase : ControllerBase
{
}

And my code uses this baseclass:

public class AdministratorController : AdminControllerBase
{
[GET("Administrators")]
public ActionResult Index()
{
return View();
}
}

But if I put the RouteArea attribute directly on this class (without use of the base-class) the issue also occurs.

Reply to this email directly or view it on GitHub:
#15 (comment)

from attributerouting.

Nice catch! Fixed in v1.1, which is available as a tasty nuget update.

from attributerouting.

Thanks a lot for your real quick support!

from attributerouting.