title: How to completely remove all items for an event which is static
body: <p>I have a class, <code>Plotter</code>, which has a static event (declared <code>public static event MouseEventHandler MultiCursorMouseMove</code> for those wondering how I have a static event).  </p>
  
  <p>It emulates a graphical plot and our current application displays about 30-40 of them. The purpose of the event is to draw a cursor across all displayed graphs to indicate the value for the graph at the time the mouse cursor is pointing at. </p>
  
  <p>The problem I'm running into is that, because the <code>Plotter</code> instances have this static event, they refuse to die. As best I can tell looking at them in a memory profiler, every instance of a <code>Plotter</code> (as well as the Form which contains them) is being held in memory by an <code>EventHandler</code> tied to this <code>MultiCursorMouseMove</code> event. I have coded set up which runs the <code>Dispose</code> method on each of the <code>Plotter</code> instances, which includes removing the delegate from <code>MultiCursorMouseMove</code>, but it doesn't seem to be doing any good. According to what I can see via the debugger, <code>Plotter.MultiCursorMouseMove</code> registers as null, but these instances still aren't getting collected and, best as I can tell via the profiler, all of the instances continue to exist due to <code>MultiCursorMouseMove</code>.</p>
  
  <p>So, the question I have is, is there any way to explicitly state "remove all delegates associated with this event"?<br>
  I figure that way I'll be sure I got rid of all of them, not to mention it will simplify things compared to my current code which, during the <code>Dispose</code> method, cycles through all of the controls on the tab and runs <code>Dispose</code> on all of the <code>Plotter</code> objects it finds.</p>
  
  <p>To be perfectly open, I <a href="https://stackoverflow.com/questions/8070094/c-sharp-trying-to-find-remaining-eventhandler-preventing-control-from-going-ou">submitted this question last week</a> but after saying it was solved, I found another issue. I tried editing the question, but it seems to have fallen out of public view.</p>