Home/ Questions/Q 658115
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T22:53:52+00:00

Currently I am using ViewData or TempData for object persistance in my ASP.NET MVC

  • 0

Currently I am using ViewData or TempData for object persistance in my ASP.NET MVC application.

However in a few cases where I am storing objects into ViewData through my base controller class, I am hitting the database on every request (when ViewData[“whatever”] == null).

It would be good to persist these into something with a longer lifespan, namely session. Similarly in an order processing pipeline, I don’t want things like Order to be saved to the database on creation. I would rather populate the object in memory and then when the order gets to a certain state, save it.

So it would seem that session is the best place for this? Or would you recommend that in the case of order, to retrieve the order from the database on each request, rather than using session?

Thoughts, suggestions appreciated.
Thanks
Ben

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I believe this is what Session was designed for – to temporarily store session specific data.

    However, due to increased complexity connected with using the Session, even if negligible – in my own ASP.NET MVC project, I have decided to hit the database on every Order creation step page (only ID is passed between the steps). I am ready to optimize and start using session as soon as I will see that the extra database hit for every request is a performance bottleneck.

    • 0