Using code blocks or Dispose method hasn’t used in this MSDN example about dialog boxes.
But why it is not disposed despite it has Dispose method ?
Using code blocks or Dispose method hasn’t used in this MSDN example about dialog
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Using code blocks or Dispose method hasn’t used in this MSDN example about dialog boxes.
But why it is not disposed despite it has Dispose method ?
Hmya, that is not crystal clear unfortunately. OpenFileDialog and friends inherit Dispose() from the Component class. Every component must implement Dispose() because the Dispose() method of the form calls it. It just so happens to be that there are several Component derived classes that have a do-nothing Dispose() method. The dialog classes are like that, they are dialogs. They clean up any unmanaged resources when the dialog closes. No additional help is needed.
This isn’t exactly documented well. It’s somewhat visible, the MSDN Library shows that the method was inherited, not overridden by the class. Which still doesn’t make it obvious that bypassing the inherited Component.Dispose() method is okay (it is). If you are uncomfortable with it, many programmers are, then don’t hesitate to wrap it with the using statement. It does no harm to call a Dispose() method that doesn’t do anything. Well, not the kind of harm you’d be ever be able to measure.