Since Microsoft suggests not using the hungarian notation anymore, does
anyone know of an arcticle defining a suggested naming convetion for vb.net?

Thanks,
Paul

Recommending naming conventions is like recommending
religions--sensible people don't go there. Just pick one you like, or
invent one, it doesn't really matter (just don't adopt the selfish
convention--using "My" as a prefix for everything <g>). The main point
of a naming convention is that it makes your life easier because your
code is more readable, at least as long as you're consistent in using
it, that is.

-- Mary
MCW Technologies
http://www.mcwtech.com

On Thu, 18 Jul 2002 17:08:19 -0500, "Paul McBride"

Paul,

See "Design Guidelines for Class Library Developers"

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpge...
ml/cpconnetframeworkdesignguidelines.asp

This is also in the VS.NET online help. The naming convention is similar to
Java. Main difference is methods and properties are Pascal case, i.e., start
with upper case.

You can adopt the same for VB.NET except you have to be slightly different
with properties because of case-sensitivity, e.g.,

Private _customer As Integer

Property Customer
...
End Property

For controls most developers (as far as I can tell) are still using
Hungarian prefixes, i.e.,

lblCustomer, txtCustomer, lvwCustomer, etc.

but I guess we should really be writing

customerLabel, customerTextBox and so on...

It should also be noted that Microsoft do not consistently follow their own
naming conventions!

Kevin

Got to :
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbco...
l/vbconobjectnamingconventions.asp