ASP.NET MVC – TempData – Good or bad practice

by

No need to have an aversion to TempData… But if not used correctly it could surely be an indication of poor design. If you are using RESTful URL’s, TempData is a best practice for transfering messages from your POST Actions to your GET Actions. Consider this:

You have a form at URL Products/New. The form Posts to Products/Create, which validates the form and creates the Product, On Success the Controller redirects to URL Products/1 and on error would redirect back to products/New to display Error Messages.

Products/1 is just the standard GET action for the product, but we would like a message to display indicating the insert was a success. TempData is perfect for this. Add the message to TempData in the Post Controller and put some if logic in the view and your done.

On failure I’ve been adding the values entered in the formCollection and a collection of error Messages to TempData in the Post Action, and redirecting to the intial Action Prodcuts/New.
I’ve added logic to the view to populate the form inputs with the previously entered values along with any error messages. Seems nice and clean to me!

More Related Contents:

  1. Using Tempdata in ASP.NET MVC – Best practice
  2. TempData keep() vs peek()
  3. When to use TempData vs Session in ASP.Net MVC
  4. How can I disable session state in ASP.NET MVC?
  5. MVC 4 Razor File Upload
  6. Getting “A potentially dangerous Request.Path value was detected from the client (&)”
  7. How do I write unencoded Json to my View using Razor?
  8. Encrypted configuration in ASP.NET Core
  9. ASP.NET MVC 3 client-side validation with parameters
  10. How to localize ASP.NET MVC application?
  11. Including an anchor tag in an ASP.NET MVC Html.ActionLink
  12. ASP.NET MVC3 and Entity Framework Code first architecture
  13. MVC3 unobtrusive validation group of inputs
  14. Can’t Add View from Controller in VS 2015 : “There was an error running the selected code generator”
  15. MVC Razor @foreach
  16. Why do we use ViewModels?
  17. ASP.NET MVC – Custom validation message for value types
  18. ASP.NET MVC: Route with optional parameter, but if supplied, must match \d+
  19. Context.User.Identity.Name is null with SignalR 2.X.X. How to fix it?
  20. What is the best ways to bind @Html.DropDownListFor in ASP.NET MVC5?
  21. IIS hijacks CORS Preflight OPTIONS request
  22. ASP.NET MVC and mixed mode authentication
  23. Adding a css class to select using @Html.DropDownList()
  24. Recursion in an ASP.NET MVC view
  25. Using an MVC HtmlHelper from a WebForm
  26. Prevent IIS from serving static files through ASP.NET pipeline
  27. MVC 4 ignores DefaultModelBinder.ResourceClassKey
  28. Working with the Output Cache and other Action Filters
  29. Load PartialView with using jquery Ajax?
  30. MVC Forms LoginUrl is incorrect

Leave a Comment