You can use TempData. TempData[“info”] = “The account has been created.”. TempData exists exactly for this situation. It uses Session as storage, but it will not be around after the second response. From MSDN: A typical use for a TempDataDictionary object is to pass data from an action method when it redirects to another action … Read more
Try using TempData. It is like a single-shot session object. You put values you want into TempData, immediately redirect and get them out. There is a good writeup here: http://blogs.teamb.com/craigstuntz/2009/01/23/37947/
RedirectToAction is just a helper method to construct a RedirectToRouteResult(), so what you do is simply create a new RedirectToRouteResult() passing along a RouteValueDictionary() with values for your action. Complete sample based on code from @Domenic in the comment below: public class IsGuestAttribute: ActionFilterAttribute { public override void OnActionExecuting(ActionExecutingContext filterContext) { if (!Ctx.User.IsGuest) { filterContext.Result … Read more
I had to solve this problem today myself, and came across this question. Some of the answers are useful (using TempData), but don’t really answer the question at hand. The best advice I found was on this blog post: http://www.jefclaes.be/2012/06/persisting-model-state-when-using-prg.html Basically, use TempData to save and restore the ModelState object. However, it’s a lot cleaner … Read more
You can supply the area in the routeValues parameter. Try this: return RedirectToAction(“LogIn”, “Account”, new { area = “Admin” }); Or return RedirectToAction(“LogIn”, “Account”, new { area = “” }); depending on which area you’re aiming for.
Did you try this?: return RedirectToAction(“action”, “controller”, new { area = “area” });
You can pass the id as part of the routeValues parameter of the RedirectToAction() method. return RedirectToAction(“Action”, new { id = 99 }); This will cause a redirect to Site/Controller/Action/99. No need for temp or any kind of view data.