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:
#if DEBUG
     //Some code
#endif
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.
[Conditional("DEBUG")]
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()
     {
          DoSomething();
     }     
     [Conditional("DEBUG")]
     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.

Comments

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

    ReplyDelete
  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.

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

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP