Skip to main content

Null object pattern - design pattern

Acest design pattern ar trebui sa ne ajute pentru a elimina sau cel putin sa reducem numarul de verificare de genul:
If( obj != null )
//Ceva cod.
Pentru a putea folosi acest design pattern este nevoie sa declaram o instanta a unui obiect( sau o clasa) care sa joace rolul obiectului care reprezinta valorea null. Exista doua varinte de implementare, de la caz la caz se poate folosi una din ele.
In prima varianta se foloseste o instanta a clasei care joaca rolul de valoarea NULL. Aceasta este oferita dezvoltatorului prin intermediul unei propietati statice.
public class Car
public static readonly Car NullObj;

static Car
NullObj = new Car();
//Setare valori, propietati cu valori default.
Deoarece am declarat field-ul ca fiind read-only, setarea acestuia se va putea face doar in constructor. Codul pe care o sa il folosim acuma o sa fie asemanator cu:
if( car == Car.NullObj )
//Executa ceva
In cazul in care vrem sa apelam metode sau propietati, putem le apelam fara sa facem verificarea daca obiectul este NULL sau nu. O sa putem scrie fara probleme cod de genul:
O alta varianta care se foloseste cand lucram cu clase abstracte sau cu interfete este sa ne declaram o clasa care sa reprezinte valoarea NULL. Iar aceasta clasa o sa poata fi folosita cand nu avem o instanta a clasei dorite si care poate sa aiba un comportament mai special, de exemplu sa faca o logare.
public abstract class Car
public static readonly Car NullObj;

static Car()
NullObj = new NullCar();
//Initializare custom daca este nevoie;

public class NullCar : Car
//Implementare custom pentru clasele abstracte sau virtuale.
Toate valoriile care o sa reprezinte instance NULL din clasa Car o sa fie de tip NullCar.
Acest pattern nu se poate sa fie folosit in orice caz, dar sunt cazuri cand se preteaza foarte bine. Un caz pe care l-am identificat este cand avem un API( un serviciu) care se ocupa de notificari. Mecanismul prin care se face notificati poate sa fie configurabil( SMS,MSM, email, etc) si chiar schimbat fara sa oprim aplicatia. Pot sa apara cazuri cand acest mecanism sa nu fie configurat, caz in care ar fi nevoie sa verificam inante de a apela metoda care face notificarea daca valoarea este NULL sau nu. Pentru acest caz am putea sa avem ceva de genul:
public interface INotification
void Notify();
public class NullNotification : INotification
public void Notify
//Se poate face un login.
In acest caz, daca nu avem nici un mecanism de notificare configurat, putem ca in NullNotification sa logam aceasta problema.


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…