views:

601

answers:

2

For a user control with internal data structures that must be disposed, is the correct place to add that code to the Dispose method in the .designer.cs file, or is there an event or something we're meant to use instead?

Edit: This is a winforms user control.

+1  A: 

Could you clarify what kind of controls? ASP.NET, WinForms?

In ASP.NET you could:

protected override void OnUnload(EventArgs e){
     base.OnUnload(e);
     //Unload here...
}
Brian Chavez
+2  A: 

If you're talking about WinForms I usually take one of two approaches to solve this problem.

Approach 1

Open the Form.Designer.cs file. Inside the generated dispose method I add a call to DisposeCore. I then go back to Form.cs and add a DisposeCore method that will now be called during dispose. I add all of my dispose logic into this method.

Editing the designer file is technically not supported. However I've found that this particular edit will not be washed away when the designer regenerates code.

Approach 2

Add a event handler to Form.Disposed and do my dispose logic in the handler. This is the preferable way because it's a supported operation and won't be affected by some designer generation you have yet to encounter.

JaredPar
Of course *slap forehead*, Disposed event. Thanks
Lasse V. Karlsen
Only InitializeComponent() is regenerated. Anything else in that designer.cs is good to go. (For VS2005, at least)
Ken