Skip to main content

Access a property using reflection

Cum putem face get/set la o proprietate prin intermediul la reflection. Odata ce avem tipul obiectului care contine proprietate, este de ajuns sa apelam InvokeMember si sa specificam numele proprietatii.
private TReturn GetProperty<TReturn>(object obj, string propertyName)
{
return (TReturn) obj.GetType().InvokeMember(
propertyName,
BindingFlags.GetProperty,
null,
obj,
null);
}

private void SetProperty(object obj, string propertyName, object value)
{
obj.GetType().InvokeMember(
propertyName,
BindingFlags.SetProperty,
null,
obj,
new object[] { value });
}
BindingsFlags se poate seta printr-un OR logic, in functie de proprietatea cu care lucram( publica, privata, statica, etc). De exemplu, pentru o proprietate publica si care nu este statica putem sa avem urmatorul apel:
 obj.GetType().InvokeMember(
propertyName,
BindingFlags.Instance | BindingFlags.Public | BindingFlags.SetProperty,
Type.DefaultBinder,
obj,
new object[] { value });
O alta modalitate de a lucra cu proprietati este sa obtim o instanta la PropertyInfo pentru proprietatea noastra, iar apoi sa facem get/set pe aceasta in felul urmator:
PropertyInfo propertyInfo = obj.GetType().GetProperty(propertyName);
propertyInfo.SetValue(obj, value, null);
Nu trebuie sa uitam ca numele la proprietate este case-sensitive.
Am incercat sa compar accesul direct la o proprietate cu cel prin reflection pentru 100.000.000 de accesari. Accesul proprietatilor prin reflection este cu circa 150 de ori mai lent decat prin accesul direct a unei proprietati. Per secunda, am avut circa ~145.000.000 de iteratii pe secunda pentru accesul direct in comparatie cu circa ~940.000.000 de iteratii pe secunde pentru accesul prin reflection.
Dar codul care folosea reflection nu a fost deloc optimizat. O sa revin cu un post in care o sa facem o optimizare a codului care foloseste reflection.
Enjoy!

Comments

  1. Daca un anume property e accesat de mai multe ori, poate ar merita vazut daca e mai performant sa folosesti Expression.Property(..) si sa cache-uiesti rezultatul..

    ReplyDelete
  2. Poate vreti sa va uitati la
    https://nuget.org/packages/Hydrate

    ReplyDelete
  3. Nu prea am înțeles, de ce e nevoie să folosesti BindingFlags.Public?

    ReplyDelete
  4. Prin intermediul la BindingFlag se setaza "locatia" unde se cauta membrul dat. De exemplu se foloseste Public, cand membrul este public. Daca acesta ar fi privat atunci ar fi nevoie sa se foloseasca BindingFlag.NonPublic. Daca membrul este static atunci se foloseste BindingFlag.Static. De multe ori este nevoie sa foloseste mai multe valori folosing un OR logic('|').

    ReplyDelete
  5. Sunt curios dacă poți ignora modificatorii de acces în felul ăsta, setând valori pentru o proprietate privată sau protected chiar dacă ești afară din linia de moștenire.

    ReplyDelete
  6. Prin reflection poti sa accesezi orice field privat. Uitate peste urmatorul link si vezi ce combinatii poti sa faci.
    http://msdn.microsoft.com/en-us/library/system.reflection.bindingflags.aspx

    ReplyDelete
  7. Dar poți și seta valori pe un field privat?

    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

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