Services
Technology Web App Development Mobile App Development Windows App Development Database Development UI/UX Development Cloud Development SEO Digital Marketing Guest Posting Content Writing Artificial Intelligence Data Science ERP Development CRM Development CMS Development LMS Development Business Listing Blockchain Technology Startup Promotion
Products
Data Converter Cleaner TUC - Unit Converter Import Export Survey Manager Tweet Controller
Developer
Article Blog Forum Interview Beginner News Startup Quiz
Users
Career
Apply Job Internship
Pricing
Login Sign Up Get a Quote

interview

home / developersection / interviews / what is the difference between tempdata, viewdata, and viewbag?
Ask Question

What is the difference between TempData, ViewData, and ViewBag?

Ravi Vishwakarma 544 12 Jun 2025
c# c#
Updated 12 Jun 2025
Ravi Vishwakarma
Ravi Vishwakarma

IT-Hardware & Networking

Ravi Vishwakarma is a dedicated Software Developer with a passion for crafting efficient and innovative solutions. With a keen eye for detail and years of experience, he excels in developing robust software systems that meet client needs. His expertise spans across multiple programming languages and technologies, making him a valuable asset in any software development project.

Message

1 Answers

Ravi Vishwakarma
Ravi Vishwakarma 12 Jun 2025
Report Abuse

In ASP.NET MVC, TempData, ViewData, and ViewBag are used to pass data from controllers to views, but they differ in lifetime, usage, and behavior.

Quick Comparison Table

Feature ViewData ViewBag TempData
Type Dictionary<string, object> Dynamic (wraps ViewData) TempDataDictionary (string keys)
Lifetime Current request only Current request only Survives redirect (one request)
Purpose Pass data to view Same as ViewData, more concise Pass data across requests (e.g. after redirect)
Syntax ViewData["Name"] ViewBag.Name TempData["Name"]
Null safety Prone to key typos Prone to runtime errors Same
Use case Any type of view data Simpler syntax for view data One-time messages, redirects

Detailed Breakdown

ViewData

  • Dictionary-like object (ViewDataDictionary)
  • Available only during the current HTTP request
  • Requires type casting and string keys
// Controller
ViewData["Message"] = "Hello from ViewData";

// View
<h2>@ViewData["Message"]</h2>

ViewBag

  • Syntactic sugar over ViewData using dynamic
  • Cleaner and avoids casting, but less safe at compile time
  • Also available only during the current request
// Controller
ViewBag.Message = "Hello from ViewBag";

// View
<h2>@ViewBag.Message</h2>

TempData

  • Stores data until it is read (or next request ends)
  • Survives a redirect (RedirectToAction)
  • Backed by Session — so session must be enabled
// Controller
TempData["SuccessMessage"] = "Profile updated successfully";
return RedirectToAction("Index");

// In redirected view
@if (TempData["SuccessMessage"] != null)
{
    <div>@TempData["SuccessMessage"]</div>
}

When to Use What?

Scenario Use
Pass data to view within same request ViewBag or ViewData
Share data between controller and view ViewBag or ViewData
Pass one-time messages (after redirect) TempData
Maintain small data across requests TempData
Store model or large objects Use ViewModel instead

Tip: Reuse ViewBag/ViewData with Partial Views

Both ViewBag and ViewData are passed automatically to partial views:

@Html.Partial("_MyPartial", model) // gets the ViewData and ViewBag

Pitfalls

  • ViewBag/ViewData are not type-safe – you can mistype the key or use wrong casting.
  • TempData gets cleared after one request unless you use TempData.Keep().
MindStick Training