Skip to main content

Covarianta si contravarianta in .NET 4.0

Covarianta si contravarinata au existat de la .NET 1.0. Schimbarea pe care a adus-o .NET 4.0 a fost ca a introdus aceste funcționalități si in tipurile generice.
In teorie, un tip T este mai mare decat S, daca si numai daca S este un subtip( derivat) din T.
Din acest enunt putem sa ajungem la concluzia ca exista o oarecare unitate de masura prin care se pot descrie tipurile( in forma unui arbore). Putem sa consideram ca T este clasa de baza, iar S este clasa derivata.
Covarianta: daca Generic este mai mare sau egal decat Generic. Covarianta se folosește in special cand vrem ca de la ceva generic sa ajungem la ceva mai particular.
Covarianta ne permite sa tratam un obiect ca si cum ar fi mai sus in ierarhie. Din aceasta cauza se ajunge ca proprietățile sa fie read-only din tipul generic.
De exemplu daca avem un tip de baza Animal si doua clase care moștenesc aceasta clasa( Caine, Sarpe), in mod normal nu am putea sa avem:
public class Animal{}
public class Caine:Animal{}
public class Sarpe:Animal{}

public interface IBox<TAnimal>
{
TAnimal Obiect { get; }
}
...
IBox<Caine> caineBox = null;
IBox<Animal> animalBox = caineBox;
Pentru a putea face acest lucru avem nevoie de:
public interface IBox
{
TAnimal Obiect { get; }
}
Trebue sa tinem cont ca covarianta nu ne permite sa avem:

  • setter pe proprietatea Obiect;
  • o metoda care sa aibe ca parametru de intrare un parametru de tip TAnimal;
  • o metoda care sa aibe ca parametru de intrare un parametru de tip referinta(ref) de tip TAnimal;
Putem sa avem in schimb o metoda ce returneaza tipul TAnimal.
interface IBox
{
TAnimal GetAnimal(); // permis
void Proceseaza(TAnimal value); // nu este permis
void Schimba(ref TAnimal reference); // nu este permis

TAnimal Obiect
{
get; // permis
set; // nu este permis
}
}
Contravarianta: daca Generic este mai mic sau egal decat Generic. Contravarianta se folosește cand vrem ca de la un tip particular sa ajungem la un tip generic. Prin acest mecanism putem sa setam valori in clasa generica.
Contravarianta apare in momentul in care vrem sa avem ceva de genul:
public interface IBox
{
void Adauga(TAnimal animal);
}
...
IBox animalBox = Init();
animalBox.Adauga(new Sarpe());
Operatiile care nu sunt permise pentru contravarianta sunt:
  • o metoda nu poate returna un obiect de tip TAnimal;
  • o metoda nu poate sa accepte ca parametru de intrare un parametru de tip referinta(ref);
interface IBox
{
TAnimal GetAnimal(); // nu este permis
void Proceseaza(TAnimal value); // permis
void Schimba(ref TAnimal reference); // nu este permis

TAnimal Obiect
{
get; // nu este permis
set; // este permis
}
}
Este bine de stiut faptul ca contravarianta poate fi folosita cand este nevoie de nevoie de trecerea de la ceva mai particular la ceva mai generic. Covarianta este asemanatoare cu READ ONLY iar contravarianta cu WRITE ONLY.
Pentru mai multe informatii: http://community.devexpress.com/blogs/paulk/archive/2010/06/18/covariance-and-contravariance-in-net-4-0.aspx
O prezentare foarte interesanta: http://blog.mbharrington.org/2011/02/21/covariance-and-contravariance-in-net-4/

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…