TextBox at design time as follows: <asp:TextBox ID="mytext"
Runat="server"></asp:TextBox> Run the page and view its source.
This is what it looks like: <Input name="mytext" type="text"
id="mytext" /> As you can see, there is no problem here because
the control is contained on the page. But what happens when the
control is contained on a user control or if you are using
master pages (ASP.NET 2.0)? Let's take a look by adding a user
control to the project. Call it mycontrol.ascx. Now move the
TextBox from the ASPX file to the ASCX file. Make a reference to
this user control on the ASPX file. Set the ID of this control
to myControl. Display the page on a browser and view its source.
This is what it looks like: <Input name="myControl:mytext"
type="text" id="myControl_mytext" /> The key to this approach is
to create a client side control which is not altered by the
server side processing. One the user control, add a hidden input
field. Set the value of the input field to a literal server side
control. This should