Microsoft has naming guidelines on their website (here). Also I have the Framework Design Guidelines book.
What I could not find was a guideline about naming controls.
For example, a button, when dropped to a form, gets the typename + number, camel-cased as default name, such as ‘button1’.
This is what I do: I delete the number and add a meaningful description after. For example ‘buttonDelete’ or ‘buttonSave’.
This way you do not have to maintain a big list of controls and their abbreviated names in a guideline somewhere.
Do you agree?
I don’t have a convention as such, but I do try to be very broad with the ‘type’ portion of the name. e.g. Button, Link Button, Image Button tend to be named ‘somethingButton’. Combo boxes, radio button lists all end up as ‘somethingSelector’. TextBoxes and Calendars are ‘somethingInput’. That way I get a rough idea of what sort of control it is without the name being tied to the actual implementation. If I decide to replace an option button group with a dropdown then no need to rename!