>>>Quick question...
>>>
>>>If I have a custom control that is a button and I drop that onto a form and I call that button "Close"
>>>
>>>In the click of that button I would like to close the form that it was dropped on... So really, I'd like to define the click event of that button in the actual custom control so that whenever I drop it onto a form, there is no coding involved... It would inherit the code from the custom control... But I cannot find the equivalent of VFP's this.parent.release()...
>>>
>>>I do not see where I would be able to use: this.parent.Dispose(false); or this.Parentform.Dispose(false);
>>>
>>>Can anyone help me understand this phenomenon??
>>>
>>>Thanks,
>>>Bob
>>
>>Robert,
>>There is a few ways to handle this. One would be to create a property on your button that stores the parent form as a reference. This would require you to set that property on the button however. Are you using a specific base class of your own for your forms? You could also put code in a base class to find the button and set the property or to subscribe to an event raised by the button. Are you using just native dot net stuff or a framework of some kind? Some frameworks have a form manager class that can provide or get the current form for you. Is this Web or Windows forms?
>>Tim
>
>Hi Tim,
>
>Thank you for your response... It really is as simple as creating a form in C# and creating a custom control is C#...
>So native dot net framework, no crazy base classes or anything... I will look into what you said... I also found
>a web tutorial (http://www.akadia.com/services/dotnet_user_controls.html#Inherited%20controls) that gives me
>some direction as well..
>
>Thanks!!
>Bob

Your welcome. It looks like that tutorial uses an event to be raised by the button.. This is a good strategy, but I would put that in a base class for your form even if it is the only reason for a base class. There are lots of reasons you would want to base all your forms on a base class as you will end up adding other stuff in there over time you want all your forms to have. Then the event handler could be in the base class and you don't need it in all your forms. Keeps it simple.
Good luck
Tim