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

How to audit an Azure Cosmos DB

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

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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