User control not updating on postback speed dating bath uni
This can cause issues if you've got no way of telling which User Control you added to the placeholder, but I've implemented such a solution before without this being too much of problem.
The second side-effect is the huge amount of View State you're going to collect as your Update Panels go about their business.
At the moment I'm looking at a updatepanel with a gridview and the dropdown controls within it.
Hi all, I asked this question on SO twice (deleted the original) but I can never seem to get a response.
Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
View State is fairly evil, and when you're posting it to and from the server with every request, combined with it being very large, it can provide some severe speed issues from a user-perspective.
I'd suggest if you do want to go down this route you should try to disable View State for any controls you do not expect to retrieve data from at a later date.
Visit Stack Exchange Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. Sign up to join this community I think you need to take a step back and say "Are Update Panels the spawn of Satan? But seriously, the way you're outlining does have some fairly bad side-effects (although it's a possible strategy to go about working with dynamic content in Web Forms and I have taken a similar approach myself).
The first side-effect you'll have is that dynamically added content does not persist after a postback, so you'll have to re-add your User Control to the Placeholder at Page_Init if you want to handle any posted form data.