Skip to main content

Where clause

Mai mult ca sigur cu toții am folosit clauza where.
Pe scurt, where este folosit când trebuie sa adaugăm o constrângere la un tip generic specificat la o clasa sau la o metoda.
public class Car<TType>
where TType : ICarModel
{}
In exemplul de mai sus o sa putem folosii tipuri generice TType doar dacă implementează interfața ICarModel. In cazul in care vrem sa specificam ca tipul generic sa fie neaparat o clasa este nevoie sa ne folosim si de cuvantul rezervat class:
public class Car<TType>
where TType : ICarModel, class
{}
In cazul acesta, TType trebuie sa fie obligatoriu sa fie o clasa (nu va putea sa fie o structura de exemplu). Pentru structuri trebuie sa folosim cuvantul rezervat struct:
public class Car<TType>
where TType : struct
{}
Dar dacă vrem sa face new de un obiect de tip generic? In cazul aceasta trebuie sa specificam ca are un constructor default în clasau de where. Din păcate doar constructorul default fără parametri se poate specifica. In restul cazurilor o sa aveți nevoie de un factory sau de reflection pentru a crea noi instante din interiorul clasei Car.
public class Car<TType>
where TType : new()
{}
Gata cu introducerea, sa va zic ce vroiam de fapt. Cand avem 2 clause de where sintaxa este destul de ciudata, trebuie sa specificam de doua ori where.
public class Car<TType,TFormat>
where TType : new()
where TFormat : struct
{}
Mi se pare umpic mai ciudat ca cele doua where-uri nu sunt despartite prin virgula sau alt caracter (cuvînt rezervat).
Voua cum vi se pare sintaxa?

Comments

  1. Probabil ca sa simplifice un pic parser-ul: daca permiteau ceva de genul:
    where TType: IComparable, IEnumerable, TFormat : struct
    compiler-ul ar trebui sa se uite in avand ca sa isi dea seama ca TFormat nu e un tip de baza pentru TType, ci un tip generic..

    ReplyDelete
  2. Parserele pot fi mult mai inteligente decit sintem obisnuiti. Un exemplu bun este sintaxa Razor pentru ASP.Net MVC.

    In cazul asta, insa, cred ca "where" reprezinta cuvintul rezervat. Dupa definitia clasei poate fi o acolada deschisa, un punct si virgula sau un "where".

    ReplyDelete
  3. Dar dacă vreau sa specific încă o clasa de "where" nu mai este nevoie sa pun nici o virgula sau un alt caracter special. Mi s-a părut destul de interesant, pana ieri nici nu am observat lipsa acestui semn.

    ReplyDelete

Post a Comment

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…