Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

It seems like a fairly unstandard way of building out of pages, but that doesn't necessarily mean that it's bad. This way it can be fully dynamic without being tied to the markup. I can see advantages in a highly fluid CMS, for example.

In regards to what they generate in an HTML sense, [this answer][1] seems to cover most the controls you are asking about.

  • 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

I'm not sure if there are tools for finding this out exactly, but if you are ever in doubt, you can always view the source code that renders within your page for some sort of clue as to how its actually functioning. Just set up a very simple test project and check the output. [1]: http://stackoverflow.com/a/462013/366976https://stackoverflow.com/a/462013/366976

It seems like a fairly unstandard way of building out of pages, but that doesn't necessarily mean that it's bad. This way it can be fully dynamic without being tied to the markup. I can see advantages in a highly fluid CMS, for example.

In regards to what they generate in an HTML sense, [this answer][1] seems to cover most the controls you are asking about.

  • 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

I'm not sure if there are tools for finding this out exactly, but if you are ever in doubt, you can always view the source code that renders within your page for some sort of clue as to how its actually functioning. Just set up a very simple test project and check the output. [1]: http://stackoverflow.com/a/462013/366976

It seems like a fairly unstandard way of building out of pages, but that doesn't necessarily mean that it's bad. This way it can be fully dynamic without being tied to the markup. I can see advantages in a highly fluid CMS, for example.

In regards to what they generate in an HTML sense, [this answer][1] seems to cover most the controls you are asking about.

  • 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

I'm not sure if there are tools for finding this out exactly, but if you are ever in doubt, you can always view the source code that renders within your page for some sort of clue as to how its actually functioning. Just set up a very simple test project and check the output. [1]: https://stackoverflow.com/a/462013/366976

Source Link

It seems like a fairly unstandard way of building out of pages, but that doesn't necessarily mean that it's bad. This way it can be fully dynamic without being tied to the markup. I can see advantages in a highly fluid CMS, for example.

In regards to what they generate in an HTML sense, [this answer][1] seems to cover most the controls you are asking about.

  • 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

I'm not sure if there are tools for finding this out exactly, but if you are ever in doubt, you can always view the source code that renders within your page for some sort of clue as to how its actually functioning. Just set up a very simple test project and check the output. [1]: http://stackoverflow.com/a/462013/366976