Skip to main content

How should we treat virtual methods exposed in APIs (Part 2)

In postul precedent am descutat despre o problema care poate sa apara cand expunem intr-un API metode virtuale, care sunt apoi suprascrise de catre un alt dezvoltator. Iar o versiune ulterioara a API schimba comportamentul aplicatiei in asa fel incat suntem obligati sa schimbam codul care foloseste API expus.
Mai jos gasiti o posibila solutie la aceasta problema.
public abstract class FooBase
private void DoAction()
// Custom code that can be executed by our method.
// More custom code that can be executed by our method.

public virtual void DoActionCore()
// Some action

public class MyCustomFoo : FooBase
public override void DoActionCore()
// My custom code of MyCustomFoo that will be
// executed by DoAction method from base class.
O solutie de acest gen o sa functioneze, doar daca cel care expune API o sa o foloseasca de la prima versiune.
O alta varianta este ca metode DoActionCore sa fie declarata ca si abstracta, in cazul in care vrem sa obligam dezvoltatorul sa defineasca un comportament custom.


  1. Presupui ca atunci cind un API este creat intr-un anumit fel, el este imutabil pentru ca exista deja third party-uri care il folosesc. Dar de fapt imutabilitatea aceasta nu preclude existenta unei alte variante de API care sa faca ce trebuie.

    In alte cuvinte nu sint de acord cu ideea ca ceva merge doar daca s-a gindit cineva inainte la asta. Orice design trebuie sa fie adaptabil, iar asta este singura responsabilitate a dezvoltatorului: sa il faca astfel.

  2. Solutia asta are si un nume - template method pattern (

    E ok ca si metoda de a permite customizarea behaviour-ului unei clase cat timp nu apar ierarhii de clase pe mai mult de 2 nivele, si cat timp nu apare necesitatea ca pentru o singura metoda din clasa de baza sa se ofere mai multe puncte de extensie - in ambele cazuri template method (foarte folosit cu ceva ani in urma) duce la cod greu de inteles si de intretinut.

    1. Mersi Tudor ca acum pot sa pun titlu la un sablon pe care il cunosteam si foloseam ;)

    2. :) e doar o conventie - si eu il foloseam cu 10 ani in urma si nu stiam cum l-au botezat..


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

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…