Can anyome shed some light on advantages of one over the other? I here evryone raving about the AspPanel control... my gawd its just a Div tag lol.

---

Answering a question increases your knowledge asking a question shows your Intelligence!

or how about straight up html with a runat = server?

I use panels personally :) but I've seen span tags with runat = server -

and findControl method, and toggle visibility that way.

---

Get ready to blast your energy levels into high gear with Sedgewick Energy Drink. High powered adaptogenic herbs mixed with potent levels of B-vitamins and...

Please disregard the contents of this post.

I would avoid people who rave about Panel controls or indeed any controls. But to see the differences, just look at the class members. Panel inherits from WebControl so has all the properties & methods of a WebControl (notably Style properties and ToolTip). It also has some design-time features.

There is no advantages as such... only a slight performance gain (WebControl is faster than any HTML control with runat="server").

---

-- Justin Lovell

Thanks Jim... So you?re saying that anytime I use a html with a runat=server attribute then I would be better off using the equivalent asp:whatever if one is available. Example if I am going to use <div runat=server></div> my code will be faster(slightly) if I use asp:panel. For some reason I got rendering specific browser code tied to asp:controls. Seems early on in my Asp.Net venture one of the things that caught my attention was that it rendered code according to browser type. Probably just a misconception on my part, that cross-browser compatibility was going to be a thing of the past :) .

---

Answering a question increases your knowledge asking a question shows your Intelligence!

My name is Justin :-) . There is a ever so slight performance gain -- about every 50 requests, you will gain 0.01 seconds per html control with a runat="server" (on 1.3GHz and 256MG RAM... and quite a bit of stuff open but not too much).

The gain is minmute on an average site. And oh, with the browser rendering different HTML equivilents: it is just plain MS that put themselves first. You can bluff ASP.NET of which browser is requesting the page by editing the web.config file. It can be found under the browserCaps section. Read here for more information:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrfbrowsercapssection.asp

---

-- Justin Lovell

Jim has also couple of good control articles at AspAlliance. :-D Though not about HtmlControls vs WebControls, IIRC.

The following thread:
view post 89647

has also an example about customizing browser detection with the web.config file.

---

Thanks,

Teemu Keiski
Finland, EU

.... My name is Justin }:-) :-) .

---

-- Justin Lovell

if(Name == "Justin){


continue;


else{


no pass go and no collection of two hundred dollars;


}

Thanks Jim ..errr Name=Justin :)

---

Answering a question increases your knowledge asking a question shows your Intelligence!

LOL, not trying to go off topic but Teemu and I have been at this for a while now about my new name ;-) . And one of my friends were not in his state of mind today and called me by his sister's name... it must be written in stars to get my name wrong this month :-) .

---

-- Justin Lovell