ASP.net MVC seperate solutions with same controller name (different namespace)

Question

I have some problems when I have same controller name in separate projects. My main solution is Web forms, and I have two MVC separate projects(separate folder) , the problem If I have a controller in first project with name HomePage and same controller name in solution 2 I have an error: Multiple types were found that match the controller named 'HomePage'. This can happen if the route that services this request ('{*pathInfo}') does not specify namespaces to search for a controller that matches the request. If this is the case, register this route by calling an overload of the 'MapRoute' method that takes a 'namespaces' parameter.

The request for 'HomePage' has found the following matching controllers: Project1.Controllers.HomePageController Project2.Controllers.HomePageController

The global.asa is in the web forms solution which I added two routes map but I still have same error. Any solution to fix this issue? Can I can in the view the action with namespace @Html.Action("index", "HomePage") Thank you

How are you registering the routes? Show us some code so we can help you, thanks. — Mihail Stancescu
– Mihail Stancescu, Commented Jan 25, 2016 at 14:49
Does one of the MVC projects reference the other? The routing framework merely collects all controllers from all available namespaces and then tries to find a matching route. Therefore, it doesn't matter if it's different projects if one references the other. — Chris Pratt
– Chris Pratt, Commented Jan 25, 2016 at 15:28
Yeah I tried but it take only the first route the second have same error — WSlama
– WSlama, Commented Jan 25, 2016 at 19:28
no reference between the 2 MVC projects, the project1 have url like www.project1.com and the second is www.project2.com when i add route it work only for the first one — WSlama
– WSlama, Commented Jan 25, 2016 at 19:30

Emma Middlebrook · Accepted Answer · 2016-01-25 15:32:05Z

2

If you need to set the namespaces value when registering the route, you should do so like this:

routes.MapRoute(
        name: "RouteName",
        url: "{controller}/{action}/{id}",
        defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional },
        namespaces: new string[] { "MyNamespace.Controllers" });

By specifying the namespace, it removes the ambiguity.

answered Jan 25, 2016 at 15:32

Emma Middlebrook

8661 gold badge9 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

WSlama Over a year ago

I tried to add namespace for both but the problem the application take always the first route

Emma Middlebrook Over a year ago

Can you edit your original post and include the RegisterRoutes code so that we can see where the conflict might be?

WSlama Over a year ago

I fixed, the solution is : The second project should have an area , the first one is optional to have it

Collectives™ on Stack Overflow

ASP.net MVC seperate solutions with same controller name (different namespace)

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related