Not quite.
There are actually 3 "families" of controls to choose from:
HTML Controls are standard HTML controls that have been a part of the HTML
language for years. These are not classes, they are tags and you can only
do client-side programming with them.
HTML Server Controls are the exact same as above but have: runat="server"
added to them. These controls add server side programmatic capabilities to
the otherwise standard HTML Control. Use these controls when migrating old
web applications to .NET applications.
Web Form Controls (a.k.a. Server Controls) are .NET Classes that expose a
rich set of properties, methods and events. They are programmable on the
client and/or the server. There are some that offer the same UI as HTML
Controls but have more features and there are some that offer a much richer
UI that would take quite a bit of programming if they were to be made in
standard HTML from scratch (i.e. Calendar Control, DataGrid Control,
Validation Controls). All of these controls render to the client as HTML
and/or CSS and/or JScript. Use these when rich UI's and/or rich
programmatic capabilities are needed.
"Martin Honnen" <ma*******@yahoo.de> wrote in message
news:Ob**************@TK2MSFTNGP09.phx.gbl...
SAI wrote:
Both have "TextBox" element and "Runat server". I don't understand the
difference.
ASP.NET tries to provide controls that are close to the HTML elements and
the client-side browser object model (the HtmlControls) and controls which
are close to the API Windows developers are used to from WinForms GUI
development.
There is some overlapping functionality that way and it is up to you to
decide what you prefer.
--
Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/
