ASP.NET Control to HTML tag equivalent

Question

I'm looking for a cheat sheet that will allow me to show an HTML designer the equivalent asp.net controls for standard HTML tags. As an example the <asp:Panel> will render as an HTML <div> and an <asp:Label> will render as an HTML <span>. I've been googling this to no avail. Can someone post a link to a good cheat sheet so that the designers on this project can understand the markup on the aspx pages more clearly.

To be clear, I would like a link to a list of major ASP.NET controls, with descriptions as to how they would relate to standard HTML. It would be great if this were in PDF format or on an easy to read and print web page. The reason, in my case, would be that we have a PHP developer who is very familiar with HTML coming to work on our project, and I feel it would be useful to have a better understanding of standard ASP.NET server controls if I could hand him such a "cheat sheet".

I'm referring mainly to the .NET 2.0 framework, but we are also doing work with 3.0/3.5.

Solution 1

This isn't a simple question, as it depends on which version of .NEt you're talking about and states of controls sometimes. For example, the PANEL, in 1 & 1.1 render to a TABLE while in later versions it's a DIV.

But overall (for 2/3), here goes:

• Panel - Div

• Panel -- GroupingText="###" is Fieldset, Legend

• Label - Span

• Button - Input, Type Button

• Link Button - Href with JS Postback Script

• Hyperlink - Standard HREF

• Image Button - Input, Type Image

• Textbox -- Default is Input, Type Text

• Textbox -- Mode = Password is Input, type Password

• Textbox -- Mode= Multiline is Textarea

• DropDownList - Select

• Listbox - Select

• RadioButton - Input, Radio with GroupName

• Checkbox - Input, Checkbox

• Repeater/Listview --Complex.

• Gridview - Table

• Table - Table

• File - Input, Type=File

  That's the basics. The more esoteric controls such as the LOGIN control is a table with a bunch of odds an ends within it.

Solution 2

Stephen's list is pretty comprehensive. I'd add the following notes to it though:

Mostly it depends on the known BrowserCaps.

A 1.x Panel will render as a div in IE6+ - however in Firefox (or other "DownStream" browsers - considered DownStream because there were no details of it in the Machine.Config by default) it will render as a single cell Table - this could be resolved by supplying updated BrowserCaps for Firefox/Opera/Safari/etc, either in the Machine.Config or Web.Configs.

Also, Control Adapters can change the output - for example the CSS Control Adapters will output styled divs for most of the tabular controls (login, registration, repeaters, etc).

Note that it was announced at TechEd/PDC that ASP.NET 4.0 will have the CSS control adapters built in by default.

Solution 3

This doesn't directly answer your question, but in a lot of cases, you can add runat="server" to a regular HTML tag to make ASP.Net aware of it. That might make things easier for the designer, if you want to be able to dynamically change the page, but still allow the designer to work on it.

<div id="myDiv" runat="server"></div>
<span id="mySpan" runat="server"></span>

Edit:

One thing that I forgot to mention (as pointed out by steve_c) is that adding runat="server" will change the ID for the tag, which can be a little bit of a pain. You're kind of out of luck if you're using the ID in your CSS, but in your JavaScript you can add something like <%= myDiv.ClientID %> to get the ID that was generated by .Net.

Solution 4

htmlgenericcontrol might be of help if you need to render a specific tag

View more solutions

Comments

[steve_c]

To add to what Matt Ephraim said, you should be aware that by adding a runat="server" ASP.NET could potentially modify the id attribute of the tag in question, if that tag is inside an ASP.NET naming container.

[mbillard]

Note that LinkButton renders an anchor element (A) that does a postback on click. The HyperLink element would be more appropriate for regular anchor elements (A).

[annakata]

Panel -> div and sometimes table applies to 2.0 as well, damn thee downscaling

[meowmeow]

@Crossbrowser - very good point. @annakata - I wasn't considering downscaling when building the list. Just a generalized overview

[annakata]

also RadioButton -> input type="radio" unless I'm mistaken

[annakata]

@Stephen - pretty big gotcha though, and you mentioned the effect for 1.x

[Matt Ephraim]

That's true. I should have mentioned that.

[stephenbayer]

this is true, you can add runat to virtually any control. Here we have aspx pages already created using asp.NET server controls. We have a new designer working on it now from the PHP/HTML world, and I'm looking to give him better understanding of the server controls.

[meowmeow]

@anakata - no, Radio Buttons are bunch of inputs of type checkboxes, with the same name, though they may have different IDs. And yes, it is a pretty big gotcha, I was just explaining why I didn't think of it.

[meowmeow]

@stephenbayer - not to my knowledge. The new guy would be better served just using .NET, and then asking any questions as he thinks of them. I crossed over from PHP to .NET and didn't have any problems understanding the differences.

[birdus]

The ASP.NET control "Label" outputs a <span>, not a Label.

[meowmeow]

@birdus - I only use the asp:label when it's associated with an input control, and thus use the AssociatedControlId property. With that set to a valid input control then the ASP.Net Label spits out a LABEL element.

[Ranadheer Reddy]

and if you use GroupingText attribute for Panel, it will render as fieldset.

[iCodeSometime]

What would be the purpose of using this rather than the actual html tag?

[person27]

BrowserCaps is a broken link as of 6-14-17

[Zhaph - Ben Duguid]

@Anon234_4521 Cheers for the heads up. That feature was deprecated in .net 2.0 but was still supported up to 3.5, I've therefore updated the link to the last supported version.