Skip to main content

Cast using AS keyword

By
Cînd dorești să faci un cast .NET iți oferă mai multe posibilități. Astăzi o să vorbim despre doua dintre ele, varianta clasica, folosind paranteze și cea folosind AS.
Mod de folosire:
IEntity entity=(IEntity)student;
sau
IEntity entity=student as IEntity;
if(entity==null)
{
//do something.
}else
{
...
}
Cînd se foloseste AS trebuie sa fim atenți in cazul in care cast-ul nu se poate face, moment in care variabila o sa aibe valoarea NULL. In general o sa fie nevoie sa se verifice daca cast-ul s-a putut face sau nu.In cele mai multe scenarii din lumea reala, o sa avem nevoie ca o exceptie sa fie aruncata, deoarece este posibil ca un alt tip sau assembly sa fi fost folosit. Sunt momente cand AS isi gaseste locul. In metodele private unde s-a facut deja o validare a datelor folosite sau avem certitudinea ca datele primite sunt asa cum ne asteptam.
Dar AS mai ascunde ceva, o problema de performanta. Mecanismul care sta in spate nu este magic deloc. In spate se face o verificare simpla, dacă conversia se poate face sau nu, iar in cazul in care acesta nu se poate face se returnează null. Ceva ce noi am putea implementa in felul urmator:
IEntity=entity is IEntity?(IEntity)entity:null;
Din cauza la acesta verificare in plus AS este mai lent cu circa 40%. Dar asta nu ii un motiv să nu îl folosim in aplicațiile de zi cu zi. Probleme de performanta nu ar trebuii să apară in general, dar este bine să se tina cont de acest lucru cînd se scrie o bucata de cod unde performanta este critica.
Pentru teste am folosit următorul cod( click pe imagine pentru a vedea codul):
Părerea mea personala este să nu folosiți AS, doar in cazuri speciale unde acesta își are rostul. Poate ca pare mai ușor de scris ca un cast cu AS, dar acesta poate să cauzeze erori ciudate cauzate de valoarea null, mai ales cînd cast-ul se face într-un loc, iar variabila este apoi folosita într-o alta metoda sau este trimisa mai departe.
Labels:

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
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...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

By
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...
Post a Comment
Read more

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

By
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...
8 comments
Read more