Everyone is correct in the use of @Html.Raw() but I want to point out to be careful with this, as it can make your site susceptible to XSS vulnerabilities. I would combine the @Html.Raw(ViewBag.SomeMessage) with Microsoft’s Anti-XSS Library to make sure you do not introduce any vulnerabilities from this. Edit: The advantage of the Anti-XSS … Read more
Child actions follow a different controller/model/view lifecycle than parent actions. As a result they do not share ViewData/ViewBag. If you want to pass parameters to a child action from the parent you could do this: @Html.Action(“Child”, new { message = ViewBag.Message }) and in the child action: public ActionResult Child(string message) { … }
In your view, you have to cast it back to the original type. Without the cast, it’s just an object. <td>@((ViewBag.data as ICollection<Person>).First().FirstName)</td> ViewBag is a C# 4 dynamic type. Entities returned from it are also dynamic unless cast. However, extension methods like .First() and all the other Linq ones do not work with dynamics. … Read more
ViewBag is a dynamic dictionary. So when using ViewBag to transfer data between action methods and views, your compiler won’t be able to catch if you make a typo in your code when trying to access the ViewBag item in your view. Your view will crash at run time 🙁 Generally it is a good … Read more
ViewBag is a property of ControllerBase, which all controllers must inherit from. It’s a dynamic object, that’s why you can add new properties to it without getting compile time errors. It’s not static, it’s a member of the object. During the request lifetime, the controller instance is created and disposed, so you won’t have “concurrency” … Read more
The ViewBag is the same thing as ViewData in previous ASP.NET MVC 1 and 2. It just happens to be dynamic instead of needing to use it like a dictionary with keys. I don’t think this will replace strongly typed views at all and in fact you should use Viewdata/Viewbag as little as possible. Always … Read more
Okay – my initial answer basically said ‘no’ – time for a bit of a u-turn. It should be ‘no’ in a perfect dynamic world – but upon closer inspection it would appear that there will either be no difference (accounting for JIT magic) or it might be ever-so-slightly slower, although not enough to warrant … Read more
@if (ViewBag.Error!=null) { // Injecting JavaScript here }
Don’t use Response.Write. Instead do this: @if (ViewBag.UserExists != null) { <h3>@ViewBag.UserExists</h3> }
if you are using razor engine template then do the following in your view write : <script> var myJsVariable=”@ViewBag.MyVariable” </script> UPDATE: A more appropriate approach is to define a set of configuration on the master layout for example, base url, facebook API Key, Amazon S3 base URL, etc …“` <head> <script> var AppConfig = @Html.Raw(Json.Encode(new … Read more