Hi

I have a problem with a site I've inherited, the main page has a lot of register directives (about 30 of them) like so

<%@ Register TagPrefix="UserAddress" TagName="Delete" Src="includes/UserAddress_delete.ascx" %>
<%@ Register TagPrefix="UserAddress" TagName="Edit" Src="includes/UserAddress_edit.ascx" %>
<%@ Register TagPrefix="UserAddress" TagName="Show" Src="includes/UserAddress.ascx" %>

The further down the code there is a long case statement for every one of these like so, ActivePage and ActiveSubPage are a couple of variables defined in page_load from request.querystring.
select case activePage

Case "usermanagement"
    Select Case ActiveSubPage.ToLower
    Case "edit","add"
%>
        <USERMANAGEMENTEDIT:SHOW id="Show16" RunAt="server"></USERMANAGEMENTEDIT:SHOW>
<%
    Case "delete"
%>
        <USERMANAGEMENTDELETE:SHOW id="Show17" RunAt="server"></USERMANAGEMENTDELETE:SHOW>
<%
    case else
%>
        <USERMANAGEMENT:SHOW id="Show7" RunAt="server"></USERMANAGEMENT:SHOW>
<%
    end select

This code is running really slowly, I've traced the code through and the page_load for every one of the ascx files is getting executed before the page displays and takes several minutes.

The only way I can see to fix this is to make the case statement redirect a new page and register the ascx to that
e.g.
create user_management_edit.aspx and register the tagprefix for just edit
create user_management_delete.aspx and register the tagprefix for just delete
create user_management_show.aspx and register the tagprefix for just show

This is a fairly major rewrite but I can't see any other way around it. I'd appreciate it if anyone could let me know if there is a better way.

Regards
Graham

ICK!! You're the unfortunate victim of someone else's VERY bad page design.

In proper page construction you should hardly ever need to use the <% %> syntax of classis ASP.

The "@ Register" directives are OK and won't make the page slower. But you could remove them because my suggestion will not need them.

What you need to change is you need to remove all the instances of the controls from the markup. Then in the page's code-behind, use the same logic and dynamically load the appropriate control using the Page.LoadControl() method. Then only the page load method for the actual control you load will run. You could put an asp:placeholder control on the page in place of all the control markup.

Here's an example (It might not be perfect, coming from memory):

plcSubPage.Controls.Add(Me.LoadControl("includes/UserAddress_delete.ascx"))

This would add just the UserAddress_delete user control to the page.

-Peter