Hi everyone,
In the past, I've always left the generated #region part of a vb.net app, but I've just realised it's a good way of grouping functions which I want to hide.
I've got the following code in several of my classes - 2 or 3 procedures which would beto hide / collapse & move out of the way at once.
As I can't find diddly squat on custom #regions on the net, I want to ask if this is good practice or not? will the GC read the procedures ok if their held within a custom region? Thanks!
VB Code:
#Region "CleanupCode" Public Overloads Sub Dispose()Implements IDisposable.Dispose 'Some Code Here End Sub Protected Overrides Sub Finalize() 'More Code Here End Sub #End region




to hide / collapse & move out of the way at once.
Reply With Quote