Some doubt for .NET and HTML/Server button

  • Thread starter Thread starter Mihir
  • Start date Start date
M

Mihir

Is CLR a process or a thread? if process then name it... if thread, name its
parent process?

2. Is Garbage Colelctor a process or a thread? if process then name it... if
thread, name its parent process?

3. If HTML Button has this property runat = "server", then what is the
difference left b/w this button and Server Control button?
 
I can answer #3...

The client-side attributes and events for HTML controls are not
available to server-side code unless we include the runat="server"
attribute. Doing so makes the HTML control the equivalent of an
HTML 'server' control which exposes its attributes and event
processing to server-side code.

--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET csgallagher@ REMOVETHISTEXT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/
 
1) Neither actually. The CLR is executable code inside of a DLL
(MSCOREE.DLL). The CLR can load into one or more processes on a
machine.

2) Likewise the garbage collector is an algorithm which executes on
one or more threads in a process. Each process with the CLR loaded can
potentially have have garbage collection executing.

3) One will be an instance of System.Web.UI.HtmlControls.HtmlButton,
the other an instance of System.Web.UI.WebControls.Button. If you take
a look at the docs, there are some additional features on the
WebControls class, like a BackColor property.

Personally, I've never found a need to use the classes in
HtmlControls. I imagine one reason they are provided is to help port
existing applications to .net by just adding runat="server" to the
HTML tags.
 
Back
Top