Skip to main content

How to improve our MVVM application using CallerMemberName

Zilele astea am descoperit cateva noi atribute in .NET 4.5 care ne sunt f. utile intr-o aplicatie MVVM si nu numai.
In namespace-ul System.Runtime.CompilerServices o sa gasim cateva atribute noi care ne permite sa accesam informatii despre cine a apelat metoda, la ce linie si locatia fisierului cs. Aceste informatii ne pot ajuta cand vrem sa scriem in log anumite date. In loc sa transmitem ca si parametru de fiecare data cine face apelul, putem sa specificam prin intermediul acestor atribute. In exemplul de mai jos, o logam cine a apelat metoda, locatia fisierului care a apelato si numarul linii de cod de unde s-a facut apelul:
public void WriteLog(
[CallerMemberName] string memberName = "",
[CallerFilePath] string filePath = "",
[CallerLineNumber] int lineNumber = 0)
{
Debug.WriteLine(String.Format("{0}-{1}: {2} ", filePath, lineNumber, memberName));
}
...
WriteLog(); // apel metoda
Orice metoda care o sa apeleze aceasta metoda, nu o sa trebuiasca sa specifice nici un parametru. Fiecare parametru o sa fie rezolvat la runtime. Este obligatoriu ca acest parametrii sa aibe o valoare default.
In functie de locatia de unde apelata metoda noastra, valoarea lui CallerMemberName poate sa difere. De exemplu daca metoda noastra ar fi apelata din constructor atunci memberName ar avea valoarea ".ctor".
Mai multe informatii despre aceste 3 atribute puteti sa gasiti aici.
Acuma sa ne uitam peste un caz unde ne este de folos atributul CallerMemberName. Intr-o aplicatie MVVM, avem nevoie sa notificam ce pro pietate s-a modificat. Acest lucru se facea pana acuma in felul urmator:
public class Car : INotifyPropertyChanged
{
private string _model;
public string Model
{
get
{
return _model;
}
set
{
_model = value;
NotifyPropertyChanged("Model");
}
}

public void NotifyPropertyChanged(string property = null)
{
if (PropertyChanged != null)
{
PropertyChanged(this, new PropertyChangedEventArgs(property));
}
}
public event PropertyChangedEventHandler PropertyChanged;
}
Acuma ne putem folosii de atributul CallerMemberName pentru a specifica ce propietate s-a schimbat. Prin intermediul acestui atribut nu mai este nevoie sa specificam de fiecare data ce propietate si-a schimbat valoarea. Codul de mai sus ar atata in felul urmator:
public class Car : INotifyPropertyChanged
{
private string _model;
public string Model
{
get
{
return _model;
}
set
{
_model = value;
NotifyPropertyChanged();
}
}

public void NotifyPropertyChanged([CallerMemberName] string property = null)
{
if (PropertyChanged != null)
{
PropertyChanged(this, new PropertyChangedEventArgs(property));
}
}
public event PropertyChangedEventHandler PropertyChanged;
}
In cazul in care facem o redenumire la o propietate sau la o metoda nu o sa mai fie nevoie sa facem update la string-urile care hardcodau numele propietatii sau a metodei.
Pe .NET 4.0 in cazul in care vreti sa obtineti numele unei metoda la runtime se poate face cu System.Reflection.MethodBase.GetCurrentMethod().Name In cazul in care apelati aceasta metoda dintr-o propietate o sa obtine valori de forma:
  • get_{numePropietate}
  • set_{numePropietate}
Enjoy!

Comments

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

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 http://go.microsoft.com/fwlink/?LinkId=260882 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.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...