Skip to main content

MVC3 - After RedirectToAction ViewBag is null

Intr-un post anterior am discutat putin despre ViewBag.
Sa vedem ce se intampla daca il folosim in urmatorul mod:
public ActionResult Index()

ViewBag.Error = “some error”;
return RedirectToAction(“Error”,”Home”);
In cazul in care o sa dorim in actiune Error din controlerul Home sa accesam ViewBag.Error, o sa observam ca acesta este null. Informatile din ViewBag sunt pierdute in momentul in care se face un RedirectToAction.
O solutie destul de simpla este sa folosim TempData, care persista intre doua actiune. TempData se poate folosii cu success cand dorim sa trimitem date intre requestul current si urmatorul. Durata de viata a obiectelor din TempData, o sa fie pana la urmatorul redirect (inclusiv). Dupa momentul respective aceste date se pierd. Valoriile din TempData sunt tinute pe sesiune intre actine curenta si urmatorea actiune accesata printr-un redirect.
public ActionResult Index()

TempData.Error = “some data”;
return RedirectToAction(“Error”,”Home”);


  1. Nu e mai elegant in astfel de cazuri sa folosesti cel de al 3-lea parametru al RedirectToAction - routeValues ? (normal, cand "parametrul" e ceva de mici dimensiuni, de ex. id-ul erorii intr-o tabela cu resurse localizate)


Post a Comment

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…