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

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

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

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

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...