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

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.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…