In asp.net is there any benefit to including or not including an id property? Assume for this question that there is no programtic reason why we need an ID. (We are not manipulating the control in code behind, nor on the client).
My personal preference is only to include an Id property when I have a reason to manipulate the control and need to be able to refer to it. So I find myself always removing Image1 Label1 etc etc…
Answers so far:
- Keeping them can help assisted technologies.
- Keeping them can help with test suites
- Removing them can have an impact on bandwidth
- Removing them keeps your intellisense cleaner (just added this one)
Having ID properties are useful for testing your page with a tool like Quick Test Pro, etc. They’re also useful for blind users who browse with a screen reading tool.
There’s a good Hanselminutes podcast where this is discussed: http://www.hanselminutes.com/default.aspx?showID=143