Skip to main content

Dispose pattern - using statement

In .NET nu trebuie sa facem dispose manual la obiectele pe care le iniţializam. Acesta face automat dispose la obiectele pe care nu le mai folosim. GC( garbage collector) se ocupa de acest lucru, stergand din memorie obiectele pe care nu le mai folosim.
Totuşi, exista momente când dorim sa controlam aceasta acţiune. De exemplu sunt cazuri când accesam baza de date, fişiere şi/sau resurse din COM. Ori avem alte obiecte în interiorul obiectului nostru care folosesc acest mecanism şi dorim sa facem dispose la ele. In aceste cazuri dorim sa controlam acţiunea de dispose. Cand spun sa o putem controla ma refer la doua lucruri separate:
  • momentul când se face "dispose";
  • acţiunea care sa se execute când se face dispose;
Pentru a putea controla acest mecanism trebuie sa implementam interfaţa IDispose. Nimic complicat pana aici, avem doar o metoda void Dispose() pe care trebuie sa o implementam. In interiorul ei putem sa facem acţiunea de dispose.
public class ProcessData: IDispose
{
private Stream _fileStream;
//....
public void Dispose()
{
_fileStream.Dispose();
}
}
Pentru a putea folosii acest pattern, putem sa folosim doua mecanisme.
Primul din ele este sa iniţializam obiectul într-un block try/catch, iar în zona de finally sa apelam Dispose().
var processData = null;
try
{
processData = new ProcessData();
//...
}
//Catch este optional.
catch(Exception ex)
{
...
}
finally
{
if(processData != null)
{
processData.Dispose();
}
}
Al doilea mecanism, care este mult mai elegant este prin folosirea lui using. Este doar un syntax sugar, care apelează in mod automat Dispose() în momentul în care se iese din block-ul using. Poate sa fie folosit doar pentru obiectele ce implementează interfata IDispose.
using(processData=new ProcessData()
{
//Executa ceva.
}
In mod automat după ce se iese din block-ul using, se va apela metoda Dispose(). Aceasta se va apela şi in momentul in care se arunca o excepţie din interiorul block-ului using.
Atenţie, nu înseamna ca după ce am ieşit din block-ul care aparţine la using, obiectul processData a fost eliberat din memorie. GC nu eliberează automat resursele ocupate de către acest obiect. Obiectul este marcat pentru ştergere, iar GC o sa ajungă într-un anumit moment sa facă dispose la acest obiect. using ne garantează doar ca metoda Dispose() o sa fie apelata în momentul în care se iese din acest block. In interiorul metodei Dispose() trebuie sa facem eliberarea resurselor pe care le ţinem ocupate sau pe care le putem controla

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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.51 EF 6.0.2 VS2013 It see...