When is it not possible to use webbserver controls

[Tony Johansson]

Hello!

I just wonder do I ever have to use the older HTML control at any time.
It would be better to only use the webbserver control.

So when is it not possible to use webbserver control

//Tony

 

[Gregory A. Beamer]

I just wonder do I ever have to use the older HTML control at any
time. It would be better to only use the webbserver control.

So when is it not possible to use webbserver control

In general, there is no reason to use the HtmlControls. The main reason
they are there is for two things:

1. Your designers design in pure HTML
2. You have legacy code but no time to retool

The HTML Control model is request/response. See:
http://tinyurl.com/yh4eq3y

You have to work through the response and create the output. There are
some helps when using runat=server, but no automagic stuff.

If you go with the web server controls, you have a better model as far
as linking things together is concerned.

The only time I would consider using HTML controls, except as noted
above, is if I hit a wall and could not figure a way to use the web
server controls.

Peace and Grace,

--
Gregory A. Beamer (MVP)

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************

 

[bruce barker]

the webserver controls offer better abstraction and hide the html they
generate. if you are server based and don't plan on complex javascript
they are a better choice.

if you are using a lot of javascript, they are a pain because you have
to reverse engineer the html produced, and hope it doesn't change. here
html controls shine, because you know the whats going on.

but if you have a new project, and want to use javascript the mvc
library may be the best choice.

-- bruce (sqlwork.com)