You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@bojanivancev Hi, I know I haven't tested it much with areas so that's probably the culprit that it just doesn't work with areas.
The error itself if I remember correctly is that there's 2 identical routes meaning the RouteDataConvention has created 2 identical routes, most likely because of the areas. Since you have 2 Home controllers for 2 different areas.
I'll try and find time to look into it and add Area support if I can.
But for now the best answer I can give you is that I don't think it's compatible with areas sadly. At least not if the controller shares the same name.
AmbiguousActionException: Multiple actions matched. The following actions matched route data and had all constraints satisfied:
MyProject.WebApp.Controllers.HomeController.Index (MyProject.WebApp)
MyProject.WebApp.Areas.Admin.Controllers.HomeController.Index (MyProject.WebApp)
I am issuing this problem when i am using areas... i.e. admin and identity area on this project...
so far, my routes look like this
routes.MapRoute(
name: "areaRoute",
template: "{area}/{controller=Home}/{action=Index}/{id?}");
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}",
defaults: new { culture = LocalizationRouteDataHandler.DefaultCulture }
);
This was working before i put your code in place...
Do you have any suggestions?
thanks in advance
The text was updated successfully, but these errors were encountered: