* What is an ascx file?

Is the extension name of the user control file

When used, add
<% @ Register tagprefix = "xxxxxx" tagname = "XXXXXXXX" src = "XXXXXXX. ascx" %>
Then you can use it.
For example:
<% @ Register tagprefix = "uc1" tagname = "headermenu" src = "ascx/headermenu. ascx" %>

<Table>
<Uc1: headermenu id = "headermenu1" runat = "server"> </uc1: headermenu>
</Table>

 

 

This concept is different from the server-side include concept. The difference is that every user control placed on a page exists in its own namespace. Anyone who tries to use the server to include (the latter contains the script block of the server) on the traditional ASP page will immediately see the benefits of the namespace. If you have already tried it, it is easy to see that the traditional ASP page will generate a compilation error due to the redefinition of variables and script processes. During development using user controls, each instance of the control exists in a unique namespace on the page, therefore, the variable names and process names used in the user space do not conflict with each other, so you do not need to consider the number of instances on a page. TheCodeAnd functions can be accessed through a specific instance of the control.