ViewBag property in MVC


The ViewBag property is typed as dynamic, which means that there is no IntelliSense.
ViewBag is alias/alternative syntax for accessing the ViewData dictionary. The two following lines of code are equivalent:

ViewBag.Message = "My message";
ViewData["Message"] = "My message";

ViewBag offers a slightly terser syntax than ViewData. Also notice that accessing ViewData using string keys also provides no IntelliSense, so you don't really lose any functionality.

One last note is that ViewBag and ViewData use the same backing storage, so that setting a property using one method makes it available using the other method:

ViewBag.Message = "My message";
string message = ViewData["Message"];

// message is now "My message"

Comments

  1. jay KumarFriday, May 03, 2013 6:58:00 pm

    yes nice understanding abut Viewbag and ViewData

    Viewbag used the dynamic feature that was introduced in c#4.0 . It allows an object to have properties dynamically added it it so can we used this view bag with c# 3.5

    Both view bag and view data does not provide the compile time error for example mis spelles key or property name you would not get any compile time error , you get to know about error only at run time , Internaly view bag properties are stored as name/value pairs in the view data dictionary .
    so i thing it always good practice to use strongly typed models
    i m new in MVC if m wrong please correct me.
    thanks

    ReplyDelete

Post a Comment

Popular posts from this blog

Customize User's Profile in ASP.NET Identity System

Image
Note: You should read this post instead, I found below walkthrough will not work on ASP.NET Identity 2. I will re-work on this post soon. In this post you will learn how to customize User’s Profile and add some more fields like FirstName, LastName, EmailID etc with ASP.NET Identity System. In my last post I listed some of the great new features introduced with Identity system .
Read More »

Migrating database from ASP.NET Identity to ASP.NET Core Identity

Image
As you know ASP.NET Core Identity (table structure) is different from what we had earlier in ASP.NET Identity. Actually the identity system which we have today with .NET Core is very mature and continuously evolved be it ASP.NET Membership, ASP.NET Identity 1, ASP.NET Identity 2 and now ASP.NET Core Identity. Recently I had to migrate few application to ASP.NET Core and similar its identity database. Because the table schema is changed, i had to re-think and create migration script which I would like to share with you today. It is very simple and easy, just three step and I had everything ready: STEP 1 : Change name of existing tables STEP 2 : Create ASP.NET Core Identity tables STEP 3 : Migrate data from old tables (ASP.NET Identity) to new tables (ASP.NET Core Identity) Script:  https://gist.github.com/itorian/c699e8534b392a6c726ec66c48100072 You should also watch my video, where I demoed migration.
Read More »