Skip to main content

Dispose and finalize

Am avut o discutie zilele astea cu un coleg despre Dispose() si Finalize(), despre modul in care se apeleaza cele doua. O sa prezint pe scurt cele doua metode.
Pentru a implementa metoda Dispose() este nevoie sa implementa interfata IDispose(). Aceasta metoda nu primeste nici un parametru. Se apeleaza de catre dezvoltator cand se doreste sa se elibere resurse folosite de aceasta entitate.
Resursele unmanaged sunt eliberate prin intermediul acestei metode si reprezinta reponsabilitatea utilizatorului.
Pana aici totul este destul de clar.
public class ProcessData: IDispose
private Stream _fileStream;
public void Dispose()
Inainte sa explic ce face metoda Finalize si de cine este apelata vreau sa explic cum functioneaza pe scurt GC:
  • Cauta toate resursele (obiectele) managed care sunt referite in codul managed;
  • Incearca sa faca Finalize pe obiectele care nu mai sunt referite in cod;
  • Elibereaza obiectele care nu mai sunt referentiate;
  • Elibereaza spatiul din memorie ocupat de acestea;
Metoda Finalize() este apelata de catre GAG si reprezinta procesul in care GC elibereaza resulsele inainte sa distruga instanta unui obiect. Acesta ar trebuii sa elibereze doar resulsele externe care sunt referentiate. Aceasta metoda este apelata in mod automat, nu se poate controla (in general) momentul in care se apeleaza.
Trebuie avut grija cand se implementeaza aceasta metoda deoarece ordinea in care care se apeleaza Finalize() nu poate sa fie controlata.
Cea ce este bine de stiut, este ca in momentul in care se implementeaza Finalize() si Dispose() se recomanda ca Finalize() sa execute si codul care apare in Dispose(). GC nu o sa apeleze niciodata Dispose().
Totodata metoda Finalize() trebuie sa apeleze obligatoriu base.Finalize(), recomanda intr-un bloc finnaly:
protected override void Finalize()
//Code Cleanup
Urmatoarele reguli trebuie respectate cand se implementeaza Finalize():
  • Trebuie sa fie mereu protected;
  • Trebuie sa apeleze base.Finalize();
  • Trebuie sa elibere resursele unmanaged;
  • .NET nu garanteaza ca Finalize() se va executa pentru fiecare instanta separat intr-un anumit moment;
  • Nu faceti new aceasta metoda;
  • Nu aruncati exceptii din Finalize();
  • Nu il definiti in date de tip value type;
  • Nu implementati Finalize() cu body gol, deoarece se consuma resurse fara rost;
Acest mecanism trebuie sa fie considerat un mecanism de fallback. Pentru eliberea resurselor se recomanda sa se folosesca Dispose(), iar Finalize() sa apeleze la randul lui codul care se executa in Dispose().
Dar Dispose() nu face release la obiect. In cazul in care dispose-ul elibereaza resursele, atunci nu mai este nevoie sa executam si Finalize(). Pentru a spune la GC sa nu mai ruleze Finalize() trebuie sa scriem urmatoarea linie de cod in metoda Dispose():
Mai jos gasiti un exemplu cum sa se apeleze Dispose():
class StoreManager: IDisposable
private bool isDisposed = false;

~StoreManager: ()

protected void Dispose(bool disposing)
if (disposing)
// Dispose la resurse

isDisposed = true;

public void Dispose()

Parca Finalize() si Dispose() sunt mai clare acuma.


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 …

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

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

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…