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...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...