Skip to main content

When Session_End is called

Intr-o aplicatie web, avem doua metode in Global.asax.cs care se apeleaza in momentul in care o sesiune este creata sau cand aceasta se termina:

  • Session_Start
  • Session_End

Daca Session_Start este apelat cand o sesiune este create, trebuie avut grija cu Session_End. Exista cateva cazuri cand aceasta metoda nu este apelata:

  • Este apelata doar daca sesiune este “InProc”. Daca tinem sesiune in AppFabric Cache sau pe SQL Server atunci Session_End nu o sa fie apelat.
  • Cand userul inchide browerul. Din cauza ca protocol HTTP este stateless, nu aveti cum sa detectati acest eveniment by default. In functie de brower acest eveniment se poate detecta, dar nu va face trigger la Session_End by default.
  • Daca in sesiune nu aveti nici o informatie atunci metoda Session_End nu o sa fie apelata.

Aceasta metoda este apelata de catre un worker processor. Din aceasta cauza pe thread-ul respective nu o sa aveti acces la toate resursele, chiar daca in Session_Start le-ati avut pe toate. De exemplu daca va conectati la o baza de date cu contul de Windows, conexiunea o sa mearga pe Session_Start, dar pe Session_End nu o sa puteti accesa baza de date.

Metoda Session_End este in urmatoarele cazuri:

  • Cand dupa un anumit interval de timp sesiune expira. Aceasta valoare se seteaza de obicei din fisierul de configurare.
  • Cand este apelata metoda Session.Abondon.

Comments

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 http://go.microsoft.com/fwlink/?LinkId=260882 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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…