In ASP.NET MVC, how does response.redirect work?

I have used response.redirect in classic ASP and ASP.NET webforms. However, with MVC 2.0, I am running into something peculiar.

I 开发者_Python百科have a private method in a controller class that is used by multiple controller methods to help load and validate some information. This private method is setup to redirect if a problem is discovered to a generic error message page.

The big problem I am noticing is that the calling controller class and page view attempt to complete rendering and loading before the redirect actually takes place. This is annoying in development because the View throws exceptions that I need to ignore before my generic error page finally loads.

As mentioned above, I am used to the older model of response.redirect which prevented subsequent code on a page from being executed as the new page would then load.

Any help or advice on redirects in MVC would be greatly appreciated.

The conventional mechanism to redirect in ASP.Net MVC is to return an object of type RedirectResult to the client. If this is done before your View method is called, your view methods will never be called.

If you call Response.Redirect yourself, instead of letting Asp.Net MVC's front controller do that for you, your controller method will continue on until it finishes or throws an exception.

The idiomatic solution for your problem is to have your private method return a result that your controller can use.

for example:

public ActionResult Edit(MyEntity entity)
{
  if (!IsValid()) return Redirect("/oops/");
  ...
  return View();

}

private bool IsValid()
{
  if (nozzle==NozzleState.Closed) return false;
  if (!hoseAttached) return false;
  return (userRole==Role.Gardener);
}

In ASP.NET MVC, you would normally redirect to another page by returning a RedirectResult from the controller method.

Example:

public ActionResult Details(int id)
{
     // Attempt to get record from database
     var details = dataContext.GetDetails(id);

     // Does requested record exist?
     if (details == null)
     {
         // Does not exist - display index so user can choose
         return RedirectToAction("Index");
     }

     // Display details as usual
     return View(details);
}

In MVC never use Response.Redirect use

return RedirectToAction("ActionResultName", "ControllerName");

As to WHY to NOT use Response.Redirect in MVC:

1. Performance issues with it
2. Not following standard asp.net MVC pattern and conventions that have been built specifically FOR MVC.

its recommended and its the only way to redirect to asp.net form in mvc controller action by using

return Redirect("/page/pagename.aspx");

other way we can redirect by using ( not recommended and bad way )

Response.Redirect("/page/pagename.aspx", true);

it will work for redirect, but problem is it will clear all of our Session values. so why its not recommended.

try this code in mvc view page lode

        if (Session["UserName"] == null)
        {
            this.Response.Redirect("LogOn");

        }