difference between HtmlControls and WebControls?

[Henri]

For instance, when should I use HtmlControls.Ht mlImage,
and when should I use WebControls.Ima ge ?

And what is the difference between
<img runat="server" />
and
<asp:image runat="server" /> ?

[Steve C. Orr [MVP, MCSD]]

The first example you gave <img runat="server"> is an HTML control.
The second example you gave <asp:image runat="server" /> is a web control.

HTML controls are quick and small and require little memory. Conversly, web
controls provide more advanced functionality than HTML controls.

If you're an old school HTML web developer then you'll find the HTML
controls to be intuitive and familiar. If you have more of a
Windows/VB/ActiveX background then you're more likely to feel at home with
the extra features that web controls provide.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"Henri" <hm********@hot mail.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

For instance, when should I use HtmlControls.Ht mlImage,
and when should I use WebControls.Ima ge ?

And what is the difference between
<img runat="server" />
and
<asp:image runat="server" /> ?

[Henri]

Very clear, thanks a lot!
:-)
To make a custom control, it seems that many control developpers inherit
WebControls. What does it add more than inheriting HtmlControl or Control?

Henri

"Steve C. Orr [MVP, MCSD]" <St***@Orr.ne t> a écrit dans le message de
news:%2******** *******@TK2MSFT NGP12.phx.gbl.. .

The first example you gave <img runat="server"> is an HTML control.
The second example you gave <asp:image runat="server" /> is a web control.

HTML controls are quick and small and require little memory. Conversly, web controls provide more advanced functionality than HTML controls.

If you're an old school HTML web developer then you'll find the HTML
controls to be intuitive and familiar. If you have more of a
Windows/VB/ActiveX background then you're more likely to feel at home with
the extra features that web controls provide.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"Henri" <hm********@hot mail.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

For instance, when should I use HtmlControls.Ht mlImage,
and when should I use WebControls.Ima ge ?

And what is the difference between
<img runat="server" />
and
<asp:image runat="server" /> ?

[Steve C. Orr [MVP, MCSD]]

HTML controls weren't designed to be extensible.
Therefore, when making your own controls you should inherit from WebControl
or Control.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"Henri" <hm********@hot mail.com> wrote in message
news:%2******** *******@TK2MSFT NGP11.phx.gbl.. .

Very clear, thanks a lot!
:-)
To make a custom control, it seems that many control developpers inherit
WebControls. What does it add more than inheriting HtmlControl or Control?

Henri

"Steve C. Orr [MVP, MCSD]" <St***@Orr.ne t> a écrit dans le message de
news:%2******** *******@TK2MSFT NGP12.phx.gbl.. .

The first example you gave <img runat="server"> is an HTML control.
The second example you gave <asp:image runat="server" /> is a web control.
HTML controls are quick and small and require little memory. Conversly,

web

controls provide more advanced functionality than HTML controls.

If you're an old school HTML web developer then you'll find the HTML
controls to be intuitive and familiar. If you have more of a
Windows/VB/ActiveX background then you're more likely to feel at home with the extra features that web controls provide.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"Henri" <hm********@hot mail.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

For instance, when should I use HtmlControls.Ht mlImage,
and when should I use WebControls.Ima ge ?

And what is the difference between
<img runat="server" />
and
<asp:image runat="server" /> ?

[Henri]

Thanks :-)

"Steve C. Orr [MVP, MCSD]" <St***@Orr.ne t> a écrit dans le message de
news:uK******** *****@TK2MSFTNG P10.phx.gbl...

HTML controls weren't designed to be extensible.
Therefore, when making your own controls you should inherit from WebControl or Control.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"Henri" <hm********@hot mail.com> wrote in message
news:%2******** *******@TK2MSFT NGP11.phx.gbl.. .

Very clear, thanks a lot!
:-)
To make a custom control, it seems that many control developpers inherit
WebControls. What does it add more than inheriting HtmlControl or Control?

Henri

"Steve C. Orr [MVP, MCSD]" <St***@Orr.ne t> a écrit dans le message de
news:%2******** *******@TK2MSFT NGP12.phx.gbl.. .

The first example you gave <img runat="server"> is an HTML control.
The second example you gave <asp:image runat="server" /> is a web control.
HTML controls are quick and small and require little memory.

Conversly, web

controls provide more advanced functionality than HTML controls.

If you're an old school HTML web developer then you'll find the HTML
controls to be intuitive and familiar. If you have more of a
Windows/VB/ActiveX background then you're more likely to feel at home

with the extra features that web controls provide.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"Henri" <hm********@hot mail.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..
> For instance, when should I use HtmlControls.Ht mlImage,
> and when should I use WebControls.Ima ge ?
>
> And what is the difference between
> <img runat="server" />
> and
> <asp:image runat="server" /> ?
>
>
>