1, work encountered such a demand, the page to all the user load out, while each user followed by the user's task to load out! My approach is to use repeater to load all the user, while in the repeater nested a GridView, the task of each user to display! The code is as follows
Foreground code:
<asp:repeater id= "Repeater1" runat= "Server" onitemdatabound= "Repeater1_itemdatabound" >
Background code:
protected void Repeater1_itemdatabound (object sender, RepeaterItemEventArgs e)
{
try
{
if (e). Item.itemtype = = ListItemType.Item | | E.item.itemtype = = ListItemType.AlternatingItem)
{
GridView GV = E.item.findcontrol ("Gv_inrep") as gridview;/ /Find the Inner Repeater object
Leader ROWV = (Leader) e.item.dataitem;//find the category repeater associated data item
string typeid = Rowv. LoginName; Gets the ID setsorting () for the populated subclass
;
Gv. DataSource = Pointdatasource (typeid);
Gv. DataBind ();
}
catch (Exception ex)
{
syslog syslog = new Syslog ();
Syslog. ListName = Constdata.listname_pcitc_ls_schedule;
Syslog. Ltype = "Repeater Item binding event exception";
Syslog. Workflowname = "Leadership Schedule management system";
Syslog. Location = "Repeater bound data: otherschedule.aspx";
Syslog. Message = "Page Information Loading exception:" + ex. message;
Syslog. DataSource = 0;
Logprovider. Addauditrecordtosource (syslog);
}