Skip to main content

Cast using AS keyword

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.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

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