MVC4 Multiple Controllers

Question

This is a very basic question, yet I cannot find any clear, simple, direct answers.

I have a basic MVC4 app with 1 HomeController.cs file. I want to create a second Controller.cs file to put more code into so HomeController doesn't turn into spaghetti code.

So obviously step 1 is to add a new controller. I assume the next step is to add some stuff to RouteConfig.cs.

What do I need to add to RouteConfig.cs to utilize a new Controller.cs?

Splitting code into two files will not fix a spaghetti code issue... if anything, it'll make it worse. Why not use proper object orientation techniques? — JDB
– JDB, Commented Sep 25, 2013 at 14:25
I don't think he actually wants to split HomeController into multiple pieces. I think he just wants to breakup the actions into different logical controllers instead of having unrelated actions all together in one file. — Trevor Elliott
– Trevor Elliott, Commented Sep 25, 2013 at 14:26
There is no need to change RouteConfig.cs if you plan to keep the pattern (controller/action/id). More about routes: asp.net/mvc/tutorials/controllers-and-routing — Felipe Miosso
– Felipe Miosso, Commented Sep 25, 2013 at 14:27
Define more code? Should you be building out another layer? — Mister Epic
– Mister Epic, Commented Sep 25, 2013 at 14:28
If you want to keep the things in different files physically, you can use Partial Class — Murali Murugesan
– Murali Murugesan, Commented Sep 25, 2013 at 15:09

Trevor Elliott · Accepted Answer · 2013-09-25 14:25:40Z

5

You shouldn't need to add anything. HomeController requires a line of code in your RouteConfig to be set as the default controller (for when users navigate to the site root), but any other controller should be accessible with the default routing.

Just create a controller, add some actions, and you should be able to route to it with the format Controller/Action or using the routing helper functions.

answered Sep 25, 2013 at 14:25

Trevor Elliott

11.3k11 gold badges69 silver badges106 bronze badges

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

Comments

George Stocker · Accepted Answer · 2013-09-25 19:11:08Z

3

What does your routes file look like?

Normally, there's a default route:

routes.MapRoute("default",
    "{controller}/{action}/{id}",
    new { controller = "Home", action="Index" }
);

That means that so long as you add a new controller with the Controller suffix, MVC will make sure the routing engine sees your controller, and as long as your URL follows the above structure, requests made in that format will be routed to the appropriate controller.

edited Sep 25, 2013 at 19:11

answered Sep 25, 2013 at 14:26

George Stocker

58k29 gold badges184 silver badges239 bronze badges

Comments

Ryan Schlueter · Accepted Answer · 2013-09-25 14:29:18Z

0

We normally send it to a different view which submits to different controllers, or add a reference in your current controller if your just wanting to call certain methods in your current home controller.

answered Sep 25, 2013 at 14:29

Ryan Schlueter

2,2212 gold badges15 silver badges19 bronze badges

Comments

Rinat Galyautdinov · Accepted Answer · 2013-10-03 10:01:51Z

0

What you really need first after creating a new controller is to add a new action (if it's not added automatically) and then add a new View for your new action. You need to touch your routes only if you are about to process some specific parameters which dont match your default settings

answered Oct 3, 2013 at 10:01

Rinat Galyautdinov

2552 silver badges2 bronze badges

Collectives™ on Stack Overflow

MVC4 Multiple Controllers

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related