2

Here the RedirectToAction() doesn't call the ActionResult Index. Do I need to register a route for this?

[ActionName("onchange")]
[AcceptVerbs(HttpVerbs.Post)]
public ActionResult OnChange(int i)
{
    m_NumberOfVisibleItems = i;           
    return RedirectToAction("Index");
}
Svante
  • 50,694
  • 11
  • 78
  • 122

2 Answers2

5

Depending on what release of MVC you're using, you don't need the [ActionName] any longer. Also, are you sure you have an "Index" action in that controller and that you don't have an [ActionName] on it that looks like this:

[ActionName("index")]

The way a lot of the stuff in MVC works is through reflection - and I believe capitalization might be an issue with that.

MunkiPhD
  • 3,636
  • 1
  • 29
  • 51
  • Hi, I tried that too as shown below but still it doesnt wrk.... [ActionName("index")] [AcceptVerbs(HttpVerbs.Get)] public ActionResult Index() {....} [ActionName("onchange")] [AcceptVerbs(HttpVerbs.Post)] public ActionResult OnChange(int i) { m_NumberOfVisibleItems = i; return RedirectToAction("index"); } –  Jul 09 '09 at 04:05
  • if you're running the RC of MVC, you don't need to have the [ActionName] decorator anymore. Try getting rid of them. Also try just returning the view: return View("Index", ); – MunkiPhD Jul 09 '09 at 11:34
3

I'm not 100% sure, but doesn't RedirectToAction send a 302 redirect to the client? So it wouldn't directly call Index(), only in the next request from the browser.

chris166
  • 4,769
  • 4
  • 24
  • 25
  • You're correct - it's an actual redirect, and as a result, the action Index should be called from scratch... so regardless of how you get there, the Index action should be called. Without more information, it might even be IIS with some sort of redirect setting issue – MunkiPhD Jul 08 '09 at 15:06