|
-
Jun 2nd, 2011, 01:28 PM
#7
Re: vb.Net guidence from a highly professioned vb.Nut such as myself.
It doesn't matter what it is... generally speaking private members are declared at the top of their containing class/block.... in other words... before your properties of that containing class/block. so I would move line 65 up to line 42... that's all I'm saying.
typically the way I've seen it (and makes most sense to me) is the following order:
-- Constants
-- Event signatures & delegates
-- private classes
-- static members
-- public members (public variables)
-- private members (public variables)
-- static properties
-- private properties
-- friend properties
-- public properties
-- static functions and methods
-- private functions & methods
-- public functions & methods
-- Event handlers (which should be private)
Just a side note... not to discourage you or anything but 2000 lines for a project isn't much... try dealing with 200 PROJECTS in an app! -eek- THAT'S when things get confusing... that's also why it's importaint that you develop habits now in consistently structuring code the same way... this way when some one looks at any project you work on, whether it's proj #42 or #42000 ... they know they will find the variables at the top... or at the bottom, or what ever the shop standard is ...
-tg
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|