Skip to main content

KeyedByTypeCollection

Cati dintre voi ati folosit pana acuma KeyedByTypeCollection? Sa va spun sincer, pana nu de mult nici nu stiam ca exista. Aceasta colectie este un dictionar unde cheile acesteia sunt reprezentate de tipul valorii adaugate in colectie.
KeyedByTypeCollection<object> collection = new KeyedByTypeCollection<object>();
collection.Add("Car");
collection.Add(1);
collection.Add(1.1);
collection.Add("Dog");  // Aceasta linie o sa arunce exceptie.
Ultima linie o sa arunce exceptie deoarece avem deja in colectie un element de tip string. La prima vedere aceasta colectie pare destul de ciudata si poate genera urmatoarea intrebare:
La ce este folositoare?Un scenariu in care aceasta colectie poate sa foarte folositoare este cand vrem sa avem un factory care sa pastreze obiectele ca si singleton. Folosind aceasta colectie implementarea factory poate sa aibe urmatoarea forma:
public class SingletonFactory<T>
{
     private readonly KeyedByTypeCollection<T> _items = new KeyedByTypeCollections<T>();

     public TItem GetObject<TItem>()
          where TItem : T, new()
     {
          if(!_items.Contains(typeof(TItem))
          {
               _items.Add(new TItem));
          }

          return (TItem)_items[typeof(TItem)];
     }
}
In ce alte scenarii de utilizare ati folosii aceasta colectie?
Enjoy!

Comments

  1. Pai cam in acelasi fel in care o utilizeaza si WCF, prin BindingParametersCollection: sa se asigure ca primeste o colectie de extensii/pluginuri/decorators/whatever de tipuri diferite (fara duplicate), deci tot un fel de sigletons in acel context...

    ReplyDelete
  2. Radu, would you please be more attentive cu privire la spelling? Prea des văd pe blogul tău, ca în postarea de față, „cheiile” sau „folosii”. Și mai sunt o groază de alte scăpări. Thanks.

    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…