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

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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…