The code below was inserted by the forms designer. The components variable
was set to null also by the forms designer. I saw no reason to override
the Dispose method in this fashion because unless the components variable
is not null it would do exactly what I think the regular Dispose method would
have been doing. Can anyone explain how this relates to components and if
it is reasonable to delete it?
/// Clean up any resources being used.
protected override void Dispose( bool disposing )
if( disposing )
if( components != null )
base.Dispose( disposing );
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL