Custom controls require no additional files beyond the .dll and are completely compiled.
User control must be deployed as an .ascx file, and the source code in the .ascx file will be visible to anyone with rights to view the files on the web server.

Custom controls can be display a design-time user interface that mimics what will be displayed at runtime.
User controls are always rendered as generic gray box.

Custom controls can be sized visually.
User controls can be sized only by setting properities.

Code to handle events exposed by custom controls can be largely generated automatically by VS.NET.
You will need to add all code by hand to handle an event exposed by a user control.

Tips
One should use a user control when reuse is only across a project.
When the control is used in a second project, take a few hours and turn it into a custom control.

if(rblGrade.SelectedIndex != -1)
{
alValues.Add(rblGrade.SelectedItem.Value);
}

Before you set SelectedValue, you need to check if it is null.

if(dr["gender"] != DBNull.Value)
{
rblGender.SelectedValue = dr["gender"].ToString();
}

http://localhost/JaneWeb/FFA/CDE/admin/CDEReportBySchool.aspx?type=fall

The key point is to overwrite ItemCreated event handler, and then design a proper footer with computed data in it.

http://aspalliance.com/494

http://www.codeproject.com/aspnet/formsroleauth.asp

Anne Morrow Lingbergh

In the new system, the admin would have the ability to configure the application by himself. This would include date and time of the events, how many teams are allowed for each school and how many members for each team. And the cool thing is all the other public registration pages and reports would be changed immediately. I don't need to go through all of them and change one by one. I don't need to worry about that I still might forget some which are supposed to be changed even though I've been tried hard. You know what? Relief!!! That's what I feel right now even though there is still a long way to finish all my coding. But I already pass the most hard part. Yeah!

My first attempt is to use web user controls at top, bottom and also having one for side menu. It works! My customers like my design. So what's wrong I have to look for another alternative?

The problem with this implementation is I have to register all the user controls in every aspx pages and create properate tags for each of them. When you have many pages in your application, you could image how bothering this could be! Plus this is costly for future maintenance.

I got to find another way to do this, I told myself. And I diving into my R&D world. Finally I find one which is easy to implement and easy to apply. I am so excited!!!!

Here is the way. You implement a master page with all fancy looks you want, header, footer, side menus. And then all other page inherit it instead of Page. That's it! Sound easy? Yes. I do satisified with this one.

----------------------------------- Below is the contribution I made------------------------------------------

Clean Up when the number of textbox was changed
By ? on Wednesday, July 19, 2006 (PST)
If we don't cleanup everytime when the requrested number of textbox was changed, error or messy would be expected. Below is my solution:

private void cleanUp()

{

TextBoxesHere.Controls.Clear();

ltlReturnData.Text = "";

}

private void txtTBCount_TextChanged(object sender, System.EventArgs e)

{

cleanUp();

}