StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4235086
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-20T21:26:03.323
FavoriteCount
0
LastActivityDate
2010-11-21T01:48:51.213
LastEditDate
2010-11-21T01:48:51.213
LastEditorUserId
417144
OwnerUserId
417144
ParentId
4234216
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The reason your events aren't happening is because you are misunderstanding the ASP.Net page lifecycle. When you request a page, ASP.Net creates a new instance of the corresponding page class. This instance knows nothing about any other instances that have been created in the past. It uses the instance of the Page class to generate a bunch of HTML, which it sends back to the browser as a response. That instance of the Page class on the server is then destroyed, along with its state. When a page posts back, ASP.Net reads through using the viewstate, ids etc and maps the HTML elements posted back to it to the server controls in your newly created Page instance. The elements you added to the Controls collection of the previous instance don't exist in this new instance, and so ASP.Net cannot recognise them, or fire events on them. Here is an article that demonstrates the kind of thing I think you are trying to achieve, albeit with GridViews, it uses a similar approach to the solution I previously posted. <a href="http://www.codeproject.com/KB/aspnet/MultiNestMDGridview.aspx" rel="nofollow">http://www.codeproject.com/KB/aspnet/MultiNestMDGridview.aspx</a> Perhaps you could explain exactly what the end goal is, because there might be a better solution? I fully accept that the limitation of both the approach I posted earlier and the solution in that link is that there are a finite number of levels of detail available, which may or may not be a problem depending on what you're actually trying to do. Edit-- If you change to the Page_Init event as @Microgen suggests, remove the if (!Page.IsPostBack), set AutoPostBack=true, and use a non-volatile ID for your dynamically added control, this will call the server side event and render the 2nd listbox. It won't work with Guid.New() because the Controls collection on the newly created Page won't contain anything with matching ID so the event handler won't get hooked up. This would answer the question as originally posted. However, your 2nd listbox won't fire events unless you create it and add it to Page.Controls in Page_Init in the same way and so on for the 3rd etc, all for the reason described above.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODynamically added ListBox's EventHandler is not firing on ASP.Net
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRichardW1001
UserOwnerUserId
1. USRichardW1001
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.