The controller for path was not found or does not implement IController

Question

I have an MVC4 project with language selection    en nl fr de   1 main part with    About Common  for the menu  Contact Faq Home   And 3 areas    Admin Customers Shop   In each area I have at least one controller  for example in Admin I have the controller overview with the corresponding view folder overview which contains an index aspx page   The home page and all the main pages  about  faq  etc   work and can be visited    However  when I follow the url  localhost xxxx en admin overview I get the error      The controller for path   en admin overview  was not found or does not implement IController    Even though the route is correct  I can see this with Route Debugger   the error page also shows that the error was thrown when I wanted to load my main menu items    lt nav id  site-navigation  class  eightcol  gt       Html Action  MenuItems    Common    lt  nav gt    -- Code removed because irrelevant --  Everything seems to be in order  but MVC doesn t seem to be able to load the menu  which is located in the main part   So  the root of the problem is  Can I grant an area  e g  Admin  access to the controllers in the main part  home  common  about  etc   of my project

User · Answer

Building on this answer by George  I found in my case that I had set my controller up properly as ThingController and I had a properly defined method on that controller Edit   But   I was referencing it in my view with   lt a href   App ThingController Edit    gt   Where I should have been just using the name without the word controller like   lt a href   App Thing Edit    gt

User · Answer

In another scenario just I would like to add is In my scenario  the name space was different for controller as it was mistake of copying controller from another project

User · Answer

This problem also occurs if you don t include your controller class for compile-process in the  csproj files    lt Compile Include  YOUR CONTROLLER PATH cs    gt

User · Answer

In my case  the same error was not related to Area but thought to post the error caused in my case  which may be helpful for the people who come to this thread by searching  The controller for path was not found or does not implement IController   The error was caused because of wrong entry in  Layout cshtml file     Styles Render    Content misc     The bundle with that name was removed in BundleConfig cs but forgot to remove it in  Layout cshtml  It was silly  but we programmers always do lot of silly mistakes

User · Answer

Not sure if this hits the solution from a different angle to the accepted answer  but I found that one of my controllers in the Areas section was sitting in the wrong namespace   Correcting the namespace to   Areas  AreaName  Controller   fixed the issue for me   I suspect the key factor was to have all the controllers within a given area share the same namespace

User · Answer

Also  for those who the solution above didn t work  here s is what worked for me   I have a solution with multiple projects  All projects were in MVC3  I installed Visual Studio 2012 in my machine and it seems that some projects were automatically upgraded to MVC4    I got this problem      The controller for path   etc etc  was not found or does not implement IController   because the project that handled that route was pointing to MVC4    I had to manually update their references to use MVC3  You can also do that by opening the  csproj file with a text editor  Find the reference to MVC3 and remove this line     lt SpecificVersion gt False lt  SpecificVersion gt

User · Answer

In my case I had    Html RenderAction  HeaderMenu    Layout   new   Area   string Empty       in  Layout cshtml but the LayoutController did not exist   I had copied  Layout cshtml from another solution but forgot to copy the controller

User · Answer

If appropriate to your design  you can make sure the access modifier on your controller class is  public   not something that could limit access like  internal  or  private

User · Answer

In my case of legacy application  the issue occurred when I added below entry in web config file under the node  lt system webServer gt           lt modules runAllManagedModulesForAllRequests  true  gt  lt  modules gt    When I removed it  the issue resolved

User · Answer

Embarrassingly  the problem in my case is that I haven t rebuilt the code after adding the controller   So maybe the first thing to check is that your controller was built and is present  and public  in the binaries  It might save you few minutes of debugging if you re like me

User · Answer

I ve found it   When a page  that is located inside an area  wants to access a controller that is located outside of this area  such as a shared layout page or a certain page inside a different area   the area of this controller needs to be added   Since the common controller is not in a specific area but part of the main project  you have to leave area empty    Html Action  MenuItems    Common   new  area          The above needs to be added to all of the actions and actionlinks since the layout page is shared throughout the various areas   It s exactly the same problem as here  ASP NET MVC Areas with shared layout  Edit  To be clear  this is marked as the answer because it was the answer for my problem  The above answers might solve the causes that trigger the same error

User · Answer

One other cause of this error  Accidental use of Html Action in a Layout file where Html ActionLink may have been intended  If the view referenced by the Html Action uses the same Layout file you effectively have created an endless loop   The layout view loads the referenced view as partial view which then loads the layout view which loads the referenced view      If you set a breakpoint in the Layout file and single step through the Htlm Action you will sometimes get a more helpful message about excessive stack size

User · Answer

In my case namespaces parameter was not matching the namespace of the controller    public override void RegisterArea AreaRegistrationContext context         context MapRoute           Admin default            Admin  controller   action   id            new  controller    Home   action    Index   id   UrlParameter Optional            namespaces  new      Web Areas Admin Controllers

User · Answer

This error can also be caused by the fact that Controllers must have  in their name  the word Controller  viz  HomeController  unless you implement your own ControllerFactory

User · Answer

Or maybe you missed keyword  quot Controller quot  at the end of controller name

User · Answer

in my case  the problem was that the controller class has not been publicly announced   class WorkPlaceController   Controller   the solution was  public class WorkPlaceController   Controller

User · Answer

This could be because the path was wrong  So check the path and the spelling of the controller first  In my case  my controller was named CampsController  and the WebApiConfig cs file had an extra path in it  Instead of  http   localhost 6600 Camps It was  http   localhost 6600 api Camps I had not noticed the api word in the WebApiConfig cs file  config Routes MapHttpRoute            name   quot DefaultApi quot             routeTemplate   quot api  controller   id  quot             defaults  new   id   RouteParameter Optional             Also it could be because the controller was incorrectly named  Here I called LayoutController  but should have called Layout instead   lt a class  quot nav-link quot  href  quot   quot  gt  Html Action  quot GetCurrentUser quot    quot LayoutController quot     lt  a gt   should be   lt a class  quot nav-link quot  href  quot   quot  gt  Html Action  quot GetCurrentUser quot    quot Layout quot   lt  a gt   Another example  it could be because you have bad Route paths defined  Make sure your paths are correct  Example      RoutePrefix  quot api camps quot       public class CampsController   ApiController      Route  quot  moniker  quot       public async Task lt IHttpActionResult gt  Get string moniker

User · Answer

In my case in global asax application start method   I was registering web api routes AFTER mvc routes like so   RouteConfig RegisterRoutes RouteTable Routes   GlobalConfiguration Configure WebApiConfig Register     Reverting the order fixed the issue  GlobalConfiguration Configure WebApiConfig Register               RouteConfig RegisterRoutes RouteTable Routes

User · Answer

In my case  I was rendering another action method for my menu section in  layout cshtml file using  Html Action  Menu    Menu   whereas I forgot to create Menu controller and as layout file was being used in my current controller action s view therefore I was getting this error in my current action render request  try to look in your layout and as well as view file if you did the same mistake

User · Answer

Yet another possible root cause for this error is if the namespace for the area registration class does not match the namespace for the controller   E g  correct naming on controller class   namespace MySystem Areas Customers       public class CustomersController   Controller                             With incorrect naming on area registration class   namespace MySystem Areas Shop       public class CustomersAreaRegistration   AreaRegistration                              Namespace above should be MySystem Areas Customers    Will I ever learn to stop copy and pasting code  Probably not

User · Answer

Somebody added this to a View   Scripts Render  quot   bundles jqueryval quot    Then they added the BundleConfig cs file in the App Start Folder  In the RegisterBundles Method they had  bundles Add new ScriptBundle  quot   bundles jquery quot   Include  quot   Scripts jquery- version  js quot      However  they forgot to finish wiring this up in the Global asax cs File  To Fix  all I had to do was add this to the Application Start Method in Global asax cs  RouteConfig RegisterRoutes RouteTable Routes    Note  I think the ordering placement of this Line in the Application Start Method matters  so please keep that in mind  I placed mine immediately after ViewEngines

User · Answer

Here is my problem and the solution that what worked for me   I added a new controller with a single action returning a string to an existing application  But when I navigated to that controller via browser  I was getting the same error as mentioned above    After doing lot of googling  I found out that I simply had to modify my Global asax cs file for it to recognize the new controller  All I did was added a space to Global asax cs file so that it is modified and it worked

User · Answer

I hope this helps someone else   I had this problem because  while I had the controller named properly  the class inside the file had a typo in it   I was looking for OrderSearch and the file was OrderSearchController cs  but the class was OrdersSearchController  Obviously  they should match  but they don t have to  and your route targets the class  not the filename

[c#] The controller for path was not found or does not implement IController

Examples related to c#

Examples related to asp.net-mvc-4

Examples related to asp.net-mvc-areas