By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,115 Members | 919 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,115 IT Pros & Developers. It's quick & easy.

HTML Client Control versus. HTML Server Control versus. Web Server Control

P: n/a
Personally, I am totally confused with the following control terms and usage
and advantages of each one in ASP.NET web application. Here's what I know so
far..

1. HTML Client Control: understood by the client only. e.g. <input
type="text" name="emp_name">
2. HTML Server Control: understood by the server only. e.g. <input
type="text" name="emp_name"
runat="server">
3. Web Server Control: understood by the server only. e.g. <asp:TextBox
id="emp_name"
runat="server"></asp:TextBox>

I tried to use all, but yield the same output. I am sure there are
advantages of each one, please advise!
Thanks!



Nov 17 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
The HTML controls (client controls) are the same HTML 4.01 controls that
have been part of the HTML language for a very long time. Use these when
their native client-side functionality serves your purpose (lowest overhead
with these controls).

The HTML Server controls are the same as above but with added server-side
programming/viewstate capabilities. Use these when migrating a "Classic
ASP" application to ASP.NET and you won't have to completely replace all
your old controls with new ones to get the .NET benefits of them. While you
do get some server-side programming capabilities with these, you don't get
the full range of properties, methods & events that pure server-side
controls offer.

The Web Form controls (a.k.a. Web Server controls) provide .NET native
server-side programming support. The properties, methods and events of
these controls are more VB like than the HTML controls. These controls
offer the widest range of flexibility from a programming standpoint, but can
(if not used correctly) create more overhead (viewstate) for your .aspx
pages.

The Web Form controls also feature controls that don't have an HTML
equivalent (validation controls, data controls, other rich controls
[calendar]). No matter which Web Form control you use, they render
themselves to the client as pure HTML/JavaScript, so they can be used in any
client!

-Scott
"Matthew Louden" <jr********@hotmail.com> wrote in message
news:ez**************@TK2MSFTNGP11.phx.gbl...
Personally, I am totally confused with the following control terms and usage and advantages of each one in ASP.NET web application. Here's what I know so far..

1. HTML Client Control: understood by the client only. e.g. <input
type="text" name="emp_name">
2. HTML Server Control: understood by the server only. e.g. <input
type="text" name="emp_name"
runat="server">
3. Web Server Control: understood by the server only. e.g. <asp:TextBox
id="emp_name"
runat="server"></asp:TextBox>

I tried to use all, but yield the same output. I am sure there are
advantages of each one, please advise!
Thanks!


Nov 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.