Skip to main content

Default value and TryParse

Ce vi se pare ciudat in urmatorul cod?
int value;
if(!int.TryParse(text.ToString(), out value))
value = 0;
In mod default, toate tipurile de numere de tip value type au valoarea default 0. Din aceasta cauza nu mai este nevoie sa setam value 0. Ajunge sa avem doar urmatorul cod:
int value;
int.TryParse(text.ToString(), out value);
In cazul in care vrem sa obtinem valoarea default pentru orice tip de data putem sa ne folosim de "default". Acest keyword returneaza null pentru toate tipurile referinta si 0 (zero) pentru value type. In cazul structuriilor acesta o sa returneze structura noastra, iar fiecare element din structura o sa fie inializat cu default value pentru acesta.
var value1 = default(int);        // 0
var value2 = default(double); // 0
public struct Point
public int x, y;
public Point(int x, int y)
this.x = x;
this.y = y;
var value3 = default(Point); // X si Y o sa fie 0
var value 4 = default(MyCustomClass) // null

In cazul in care vrem ca codul nostru sa fie mai usor de inteles putem ca in momentul in care il declaram pe value sa il setam cu default(int) sau cu 0. Eu prefer a doua varianta deoarece este mult mai usor de citit.


  1. Problema cu bucata nr.2 de cod (`int value;
    int.TryParse(text.ToString(), out value);`) este ca daca iti vine zero nu stii daca zero era efectiv in string-ul respectiv sau a esuat parse-area...

    1. Drept. In primul exemplu, se seta valoarea default la 0 daca parsa a esuat (nu mai era nevoie sa executam sau sa logam ceva daca aceasta a eusat). In al doilea exemplu se obtine acelasi comportament, valoarea default fiind setata pe 0.


Post a Comment

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

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.

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…