CODEWITHSUNDEEP
c#.netasp.net-mvc
Brian
Brian

Reputation: 21

Call an action from another controller

I have two different objects: contracts, and task orders. My requirements specify that in order to view the Details for either object, the Url should be "http://.../Contract/Details" or "http://.../TaskOrder/Details" depending on which type. They are both very similar and the details pages are almost identical, so I made a class that can either be a contract or a task order, and has a variable "objectTypeID" that says which type it is. I wrote the action "Details" in the task order controller, but now I want to call that from the contract controller instead of recopying the code.

So is there any way to have the url still say ".../Contract/Details" but call the action in the TaskOrder controller instead? I tried using

TaskOrderController TOController = new TaskOrderController();
TOController.Details(id);

This would have worked except that I can't use the HttpContext.Session anymore, which I used several times in the action.

Upvotes: 2

Views: 4071

Answers (4)

Brian
Brian

Reputation: 21

Thanks David, I should be calling it from the view.

All I needed was the following line in my Contract/Details.aspx page:

<%= Html.Action("Details", "TaskOrder", new { id = ViewData["id"] })%>

Upvotes: 0

David Neale
David Neale

Reputation: 17048

Why are you calling a controller from a controller? A controller action should be called via a route and return a view.

If you have common code used by two separate controllers then you should be looking to abstract this code to another class.

Upvotes: 1

taylonr
taylonr

Reputation: 10790

Create a base class for the controller. Like DetailsController

Put your details code in there, and have it accept an typeId. Then have your two controllers derive from that base class, and have their Details action call the base class passing in the id

Upvotes: 0

Wim
Wim

Reputation: 12092

RedirectToAction("Details","To");

In addition, add routing parameters if you need to.

Also, maybe you need a BaseController class which these two controllers inherit from and which implement the same Details action, but based on the objectTypeID do slightly different things.

Upvotes: 0

Related Questions