One limitation of using RedirectToAction("actionName", {object with properties})
is that RedirectToAction() has no overload which accepts RedirectToAction(ActionResult(), {object with properties})
, so you are forced to use magic strings for the action name (and possibly the controller name).
If you use the T4MVC library, it includes two fluent API helper methods (AddRouteValue(...)
and AddRouteValues(...)
) which enable you to easily add a single querystring parameter, all properties of an object, or the whole Request.QueryString. You can call these methods either on T4MVC's own ActionResult objects or directly on the RedirectToAction() method. Of course, T4MVC is all about getting rid of magic strings!
As an example: suppose you want to redirect to a login page for a non-authenticated request, and pass the originally requested URL as a query string parameter so you can jump there after successful login. Either of the following syntax examples will work:
return RedirectToAction(MVC.Account.LogOn()).AddRouteValue(@"returnUrl", HttpUtility.UrlEncode(Request.RawUrl));
or
return RedirectToAction(MVC.Account.LogOn().AddRouteValue(@"returnUrl", HttpUtility.UrlEncode(Request.RawUrl)));