Skip to main content

#IF DEBUG can be replaces with Conditional attribute

Pe un proiect legacy la care am lucrat anul acesta apareau destul de conditia urmatoare:
     //Some code
Natura proiectului ne obliga sa avem astfel de cod. Problema era ca uneori noi compilam proiectul configurat pentru RELEASE, faceam modificari la cod si in RELEASE totul parea in ordine, dar pe masina de build, aveam erori de compilare, deoarece acesta compila in DEBUG.
Am descoperit zilele acestea un nou atribut care poate sa inlocuiasca aceasta conditie urata.
public static void DoSomething()
     //Some code
Metoda DoSomething o sa fie apelata doar in cazul proiectul este compilat in DEBUG mode.
Cand putem sa folosim aceast atribut?
  • se poate folosi doar in interiorul unei clase sau a unei structuri. Nu incercati sa il puneti pe metoda unei interfete, deoarece o sa dea eroare la compilare
  • metoda pe care o decorati cu acest atribut nu trebuie sa fie neaparat statica, dar nu are voie sa fie implementarea  unei metode din interfata
  • metoda nu trebuie sa fie marcata cu override, dar poate sa contina atributul virtual
  • valoarea returnata de aceasta metoda trebuie obligatoriu sa fie void
Singurul lucru care poate sa  fie confusing este urmatorul cod:
public class Car
     public Car()
     public void DoSomething()
          //Some code.
Ce o sa se intample la compilare daca avem setat RELEASE? O sa avem o eroare de compilare? Se va mai apela  metoda noastra? Raspunsul este ca codul general de IL nu va include si apelul la metoda DoSomething() daca compilam pentru RELEASE.
Personal incerc sa evit sa folosesc aceste conditii, nu sunt foarte sanatoase. Dar daca lucram deja pe un proiect care contine conditii de tip #if DEBUG, pentru a refactoriza codul si a scapa de aceste conditii, primul pas este sa le scoatem ca si metode separate, decorate cu atributul Conditional.


  1. Fain - asa e implementat si Debug.Assert, de ex..

    De conditional compilation in general nu prea ai cum sa scapi cand codul contine metode proprii de logging sau profiling care trebuie sa se execute doar la debug, nu si in release..

  2. Drept. Dar macar le putem tine frumos grupate. Urasc sa dau de cod care contine atat logica cat si tot felu de conditii de compilare.

  3. Adevarul e ca in C#, care nu are un preprocessor adevarat precum C++, genul asta de directive e mult mai rar folosit..


Post a Comment

Popular posts from this blog

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 …

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

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.


Writing solid codeCode completeProgramming Pearls, more programming pearls(recommended)[NEW] Introduction to Algorithms


Refactoring (M. Fowler)Pragmatic ProgrammerClean code[NEW] Software Engineering: A Practitioner's Approach[NEW] The Mythical Man-Month[NEW] The Art of Computer Programming


Applying UML and Patterns (GRASP patterns)C++ coding standards (Sutter, Alexandrescu)The C++ programming language (Stroustrup, Part IV)Object-oriented programming (Peter Coad)P…