Skip to main content

Using Extensions Methods for DI setup

This days I saw a pretty nice idea of implementing the setup part of a DI container – when you make the setup from code and not from configuration file.
Usually when you are working with DI on a big project, you a piece of code for each component (assembly) that register into the container the instances for that component - ContainerInstaller. When you start the application or load a specific container you need to call that specific class end register all the items for that class.
public class FooInstaller
    public void Install(IContainer container)
This can be made automatically, if you define an interface like IInstaller. Using reflection or other mechanism you can automatically find this installers and run them.
Another solution that I think that is pretty interesting is to define an extension method for each component (assembly) – an extension method of builder. Each component will define internally his own extension method that do the same think as the installer.
public static class FooContainerExtension
    public static void AdFoo(this IContainer container)
In the main entry point of the application, you will need to call the extension method for each component.
This is a nice feature for develops, that don’t need anymore to look over documentation to see which installer they need to call and so on.
Of course this is not a perfect solution and will not work for big project where you need automatically to make this setup. Also, because you define an extension method directly to a specific builder (or container) you will have a direct dependency to the DI container (but how often you change it?).
In conclusion I would say that this is an interesting solution, that can be used with success for small project. This could be a great solution when you define a stack that will be used by others. They will be able to see directly what kind of installer they have available. AND, in the end the extension method can forward the call to an installer class.


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

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

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…