Skip to main content

#IF DEBUG can be replaces with Conditional attribute

By
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.
Labels:

Comments

  1. TudorNovember 26, 2011 at 1:10 PM

    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. Radu VunvuleaNovember 27, 2011 at 1:41 PM

    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. TudorNovember 28, 2011 at 10:21 AM

    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

By
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(...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more