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:


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.

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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...