Why does the WinForms default name for controls start with lowercase, but is uppercase for WebForms? What’s the likely rationale for this?
Why does the WinForms default name for controls start with lowercase, but is uppercase
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why does the WinForms default name for controls start with lowercase, but is uppercase for WebForms? What’s the likely rationale for this?
Probably lost to the depths of time, and an artifact of different teams working on different designers.
This next note doesn’t apply to the original days, but one interesting point in the current incarnation of ASP.NET is that the page inherits from the code-behind, so the proper-case names would make sense if they were exposed as protected properties. But they aren’t: they are exposed as protected fields… so that is 2 standard guidelines broken at once (non-private fields and casing of fields).