tempdata

I am using the TempData in order to preserve my model in when using a RedirectToAction . It works fine, but I have a nagging feeling that it might not be the right thing to do. I really try to avoid using Session data, and I've read that TempData uses the Session. Is it safe to use? Are there issues which might arise in using it in a load balanced environment? Trivia Question: "Is It Safe?"-- name the movie. Yes, TempData is backed by session storage, so if you are in a load balanced environment extra care must be taken when using it (sticky sessions, persistent session state, etc). TempData

Most of my action methods return PartialViews on success and RedirectToAction results on failure. For that, I would like to copy the model state errors into TempData so I could display them to the user. I've read several questions here on SO and some external links but none of them worked for me... I'm decorating the ActionMethod with ModelStateToTempData attribute from MvcContrib, then displaying it as follows in the view: (this is just a prototype) @if (TempData.Count > 0) { foreach (var obj in TempData) { var errors = ((ModelStateDictionary)obj.Value).Values; foreach (var error in errors) {

If I redirect to a new page passing TempData to initialise the page it works fine, however if the user presses the refresh button in their browser the TempData is no-longer available. Given this, is there any situation where TempData could be used reliably? Or any way to remove or mitigate the problem of users refreshing? In MVC 1, yes, temp data is lost after the next request after you store a key. With MVC 2 however, the temp data is lost after the first attempt to access it. You can always use Session, which TempData uses anyway, to solve the temp data loss issue your having. From the MVC 2

I've seen some articles (even MSDN) suggest TempData for passing data between ActionMethods. But I've seen others here say that TempData should be avoided. What's the best practices way to approach this? Here's some code to show my situation. Note: I'm 100% sure, I'm doing this wrong. Which is why I'm here. :) Also, I've been doing Webforms up until recently. Note2: This is related, but not the same. View: <div> @using (Html.BeginForm("Previous", "Home", new {month = @month}, FormMethod.Post)) { <input id="previous" type="submit" value="Previous" /> } // This fails but that's another situation

I have a site I'm playing with to get the hang of Razor Pages. I have a weird situation I'm unsure what is happening or how to resolve. I'm using [TempData] to pass a message on redirect. The app works perfectly locally. Once published to Azure I add a new item and the item is added, I'm redirected to the index page but I never see the TempData message. Here is my Index page: public class IndexModel : PageModel { private readonly TheFishRoom_MVC_Core.Data.FishRoomDbContext _context; public IndexModel(TheFishRoom_MVC_Core.Data.FishRoomDbContext context) { _context = context; } public IList

What is the actual use of TempData collection in asp.net MVC, I need pros and cons of that collection, and when do I need to use it, which views it is shared upon, or any useful information about it, finally if someone can tell me when to use it rather than ViewData? Thanks in advance CLOSED as exact duplicate of Difference Between ViewData and TempData? TempData is used to share data between controller actions. If your controller does a RedirectToAction and the target action needs data (perhaps a particular model instance) to act upon, you can store this data in TempData. Using TempData is