Naming Conventions
Where I work, we are in the process of creating a new standards document for our vb.net development efforts. We have been trying to mold ourselves to the industry standards as much as possible. Everyone has been pretty agreeable on everything until we got to the naming conventions portion (specifically regarding the naming of controls). One camp wants to follow the industry trend that says all controls should be named according to it's purpose without identification of type e.g. a text box named "FirstName". The other camp proports the traditional add-a-prefix view citing that the controls you are looking for will be grouped together in intellisense e.g. same text box named "txtFirstName". I am suprised at how passionate people are on this point. I am not trying to stir up a heated debate here, but I would really like to know how others feel on this subject. Give me your feedback. I'd love to hear it.
[This post was originally posted at my DevAuthority.com blog.
http://www.devauthority.com/blogs/dbalzer/default.aspx Go to
http://www.devauthority.com to get your own .Net blog.]