Skip to main content

Subscribe to events using reflection

·When you use reflection to load and run assemblies, you cannot use language features like the C# += operator or the Visual Basic AddHandler statement to hook up events. This MSDN document (http://msdn.microsoft.com/en-us/library/ms228976.aspx) shows how to link an existing method to an event by getting all the necessary types through reflection and how to create a dynamic method using reflection emit and link it to an event.

A sample:

   1:          // Load an assembly, for example using the Assembly.Load
   2:          // method. In this case, the executing assembly is loaded, to
   3:          // keep the demonstration simple.
   4:          //
   5:          Assembly assem = Assembly.GetExecutingAssembly();
   6:   
   7:          // Get the type that is to be loaded, and create an instance 
   8:          // of it. Activator.CreateInstance has other overloads, if
   9:          // the type lacks a default constructor. The new instance
  10:          // is stored as type Object, to maintain the fiction that 
  11:          // nothing is known about the assembly. (Note that you can
  12:          // get the types in an assembly without knowing their names
  13:          // in advance.)
  14:          //
  15:          Type tExForm = assem.GetType("ExampleForm");
  16:          Object exFormAsObj = Activator.CreateInstance(tExForm);
  17:   
  18:          // Get an EventInfo representing the Click event, and get the
  19:          // type of delegate that handles the event.
  20:          //
  21:          EventInfo evClick = tExForm.GetEvent("Click");
  22:          Type tDelegate = evClick.EventHandlerType;
  23:   
  24:          // If you already have a method with the correct signature,
  25:          // you can simply get a MethodInfo for it. 
  26:          //
  27:          MethodInfo miHandler = 
  28:              typeof(Example).GetMethod("LuckyHandler", 
  29:                  BindingFlags.NonPublic | BindingFlags.Instance);
  30:              
  31:          // Create an instance of the delegate. Using the overloads
  32:          // of CreateDelegate that take MethodInfo is recommended.
  33:          //
  34:          Delegate d = Delegate.CreateDelegate(tDelegate, this, miHandler);
  35:   
  36:          // Get the "add" accessor of the event and invoke it late-
  37:          // bound, passing in the delegate instance. This is equivalent
  38:          // to using the += operator in C#, or AddHandler in Visual
  39:          // Basic. The instance on which the "add" accessor is invoked
  40:          // is the form; the arguments must be passed as an array.
  41:          //
  42:          MethodInfo addHandler = evClick.GetAddMethod();
  43:          Object[] addHandlerArgs = { d };
  44:          addHandler.Invoke(exFormAsObj, addHandlerArgs);


Some related links:


Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more