Mike said:
I want to study nested classes. Something like this offers
constructor/destructor logic to the component class:
Public Class MyComponent
Private nestedObject as new Constructor
Public class Constructor
public sub new()
end sub
protected overrides sub finalize()
end sub
End Class
End Class
When MyComponent is instantiated, it will initialized its members. Thus
the nested Constructor class is instantiated preparing a New() and
Finalize(). Finalize() will be called here.
Make sense?
--
Just found an entire MSDN section on the usage of nested classed for
components.
Nested Classes in Components
http://msdn.microsoft.com/en-us/library/cbwxw0ye(VS.71).aspx
After reading it, I think the improvement to the .Designer.vb class
that will help resolve this issue, making it less a concern whether
you can edit or not the .designer.vb code is for the generated code
template to add a empty inheritable "destructor" or Delete() that is
called by the dispose method.
That is what i did for my SDK abstract class.
Public Class CWildcatAbstract
Implements IDisposable
Private _disposed As Boolean = False
Public Overloads Sub Dispose() Implements IDisposable.Dispose
Dispose(True)
GC.SuppressFinalize(Me)
End Sub
Protected Overloads Overridable Sub Dispose(disposing As Boolean)
If Not _disposed Then
If disposing Then
' add releasing of managed resources
_disposed = true
End If
' add releasing of unmanaged resources
Delete()
_disposed = True
End If
End Sub
Protected Overrides Sub Finalize()
Dispose(False)
End Sub
Public Overridable Function Delete() as boolean
return false
end function
End Class
So now a class that inherits this can create a Delete method that will
be called come destruction/cleanup time.
Public Class CWildcat : inherits CWildcatAbstract
Public Overrides Function Delete() as boolean
... do whatever cleanup ...
return true
end function
End class
--
