Why do we have ViewBag and ViewData if they are doing the same thing in ASP.NET Core MVC? Is there anything which ViewBag can do and ViewData can't - or vice versa?
Any specific scenario when should I prefer one over the other?
-
1ViewData is a dictionary of objects.ViewBag is a dynamic property, and is able to set and get value dynamically and able to add any number of additional fields without converting it to strongly typed. they are all used to transfer data from controller to viewRuikai Feng– Ruikai Feng2022-03-23 07:31:33 +00:00Commented Mar 23, 2022 at 7:31
-
1c-sharpcorner.com/blogs/viewdata-vs-viewbag-vs-tempdata-in-mvc1LazZiya– LazZiya2022-03-23 07:39:37 +00:00Commented Mar 23, 2022 at 7:39
Add a comment
|
1 Answer
They are similar, but the main difference is that ViewBag use dynamic types, allowing a less complex syntax.
ViewBag.Example=DateTime.Now;
<p>Result: ViewBag.Example.Year </p>
Against that, the same with ViewData could be:
ViewData["Example"]=DateTime.Now;
<p>Result: @((ViewData["Example"] As DateTime).Year) </p>
So with ViewData you need casting, and you can receive errors when perform a "renaming", and you won't have the aid of Intellisense, for example.
Additionally, it seems to be "slower" (but not enough to be a problem). Example: ViewBag vs ViewData performance difference in MVC?
2 Comments
Amit
It means, if we want speed, we should use ViewData, and if we use Ease of use we should use ViewBag.
Morcilla de Arroz
Yes, we could say that ViewBag is a wrapper over ViewData, although performance's difference is almost irrelevant,