Dynamically load the components of a user control!

Dynamic | load | Controls the purpose of our writing user controls is to put them in the page. Depending on the conditions, we can change the loaded user control!

In fact, the principle is the principle of masterpage. This masterpage will be available in vs2005, but it can now be implemented.

In my project, I use the following:



MasterPage on four classes, where the container dynamically loads the user control. This functionality will be ubiquitous in vs2005.

The following is a brief introduction to dynamically loading Foliar components:

All we need to do is change the address of the user component to dynamically change the loaded user component.

It's OK to change the Skinpath dynamically in the program.

Component source code is as follows:

Using System;
Using System.Drawing;
Using System.Collections;
Using System.Collections.Specialized;
Using System.Web;
Using System.Web.UI;
Using System.Web.UI.WebControls;
Using System.ComponentModel;
Using System.IO;
Using System.Web.Security;
Using Region.components;

Namespace Region.controls {

[ParseChildren (True)]
<summary>
page components, obtaining from the user component
</summary>
Public abstract class Skinnedcontrol:webcontrol, INamingContainer {

string skinfilename = null;
string skinname = null;
String Skinpath;

string returnurl = null;

<summary>
To add a child component
</summary>
protected override void CreateChildControls () {
if (Skinpath = null | | Skinpath = "" | | Skinpath.trim () = = "")
return;
Control skin;
Skin = Loadskin ();
Initializeskin (skin);
Controls.Add (skin);
}

<summary>
Get Touch Board Assembly
</summary>
<returns> Components </returns>
Protected control Loadskin ()
{
Control skin;
Try
{
Skin = Page.LoadControl (Skinpath);
}
catch (FileNotFoundException)
{
throw new Exception ("File not found: [" + Skinpath + "].");
}
return skin;
}

<summary>
Initializing the build Touch board
</summary>
<param name= "Skin" > Components </param>
protected abstract void Initializeskin (control skin);


<summary>
User Component Name
</summary>
public string Skinfilename
{
Get
{
return skinfilename;
}
Set
{
Skinfilename = value;
}
}

<summary>
Component Name
</summary>
Protected string Skinname
{
Get
{
return skinname;
}
Set
{
Skinname = value;
}
}

<summary>
User component relative path and component name
</summary>
public string Skinpath
{
Get
{
return skinpath;
}
Set
{
Skinpath = value;
Skinfilename = value. TrimStart ('/');

}
}




}
}


For example, one of my applications:

Switch (context. PageID)
{
Case "1_1":
Base. Skinpath = "~/themes/signmanager/termlist.ascx";
break;
Case "1_1_1":
Base. Skinpath = "~/themes/signmanager/termedit.ascx";
break;
Case "1_2":
Base. Skinpath = "~/themes/signmanager/memberlist.ascx";
break;

Case "1_2_1":
Base. Skinpath = "~/themes/signmanager/memberedit.ascx";
break;
Case "2_1":
Base. Skinpath = "~/themes/signmanager/cardsend.ascx";
break;
Case "3_1":
Base. Skinpath = "~/themes/signmanager/membernoedit.ascx";
break;
Case "4_1":
Base. Skinpath = "~/themes/acountedit.ascx";
break;
Default:
Base. Skinpath = "";
Break
}



Based on the development of the formation, we can save a lot of the surface of the duplication of places. Just refer to the component at the place where the leaf is repeated.

Like what:



So that we can take the user component as the element, the component different foliage. Foliage can also be reused!