Never call dispose unless you have a really good reason for this.
If the object contains a heavy object (image, database connection, etc.), call close as soon as you are done with it.
Calling the utility at closing will force you to reload the resource at opening. The form can be reopened if you do not destroy any important items after it is closed and save the link.
By definition, "close" does the same as "dispose" (and closes windows / forms). Each private call in the .net infrastructure simply causes a failure inside inside.
@comment
I used an application that supported 40 MB bitmaps. Call recycling on those that really helped on the memory-related machine. Calling an object to objects with the information asked in the question is impossible. Calling it โjust becauseโ is bad, calling it because the designer makes it even worse.
source share