Coding Standards & Program Structure

[DazedAndConfused]

Is it proper to structure your code in the basic work flow of the program?

i.e.
Form_Load

[Carlos J. Quintero [.NET MVP]]

You can use any layout for your functions: by proximity (usage) or by scope
(private, public, etc) or by functional groups, it's up to you and the
compiler does not care about it. Notice that VS.NET allows you to group
functions in code regions:

#Region "My private functions"
Private Sub f1()
End Sub

Private Sub f2()
End Sub
#End Region

Then you can expand/collapse the regions (The +/- signs) to see/hide the
code layout.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

"DazedAndConfused" <Ac********@yahoo.com> escribió en el mensaje
news:Il*******************@twister.nyroc.rr.com...

Is it proper to structure your code in the basic work flow of the program?

i.e.
Form_Load
.
Exclusive routines to Form_Load
.
Open_Dialog
.
Exclusive routines to Open_Dialog
.
.
.
.
Last_Routine_For_Specific_Shared_Routines
.
Shared_Routine_1
.
Shared_Routine_2
.
.
.
Another_Last_Routine_For_Specific_Shared_Routines
.
.
Shared_Routine_3
.
Shared_Routine_4
.
Form_Closing
.
Exclusive routines to Form_Closing
.
.
Shared_routine_99(ifAny)

End Class

--
How time fly's when you don't know what you are doing!
I learn when I'm wrong, I learn a lot.