Always try to assign a meaningful name to a control. If you follow this approach, you will find that the computer cannot handle it, so it must be done manually. In your case, how does he know that TextBox1 needs to identify name ?
txtName1 not a good name for the control, because a) does not tell the developer whose name it is and b) that 1 ? Does this mean the first part of the name, that is, the name? Or the name of the first person on the list? The correct name will look like txtCustomerFirstName or txtFirstCustomerFullName (for a) and b) respectively), unless you have other considerations, such as keeping the control name as short as possible, match the database field name or another reason.
Source: I have developed an enterprise-class insurance management application with more than 1000 text fields and am the main contact person to support any problems with it at the moment. In my experience, the purpose of controls is not where you spend most of your time.
As a note, if you manually rename the control through the constructor, it will also rename all its uses in the code. This greatly reduces the work that needs to be done.
Neolisk
source share