K
kw
I've developed about a dozen sites with ASP.net and never had much
trouble...until now.
What I wanted to do with the new web app was create a single page with a
treenode collection that would dynamically load content into a placeholder.
I ran into two showstoppers:
1)"The control tree into which viewstate is being loaded must match the
control tree"... Meaning that you can't navigate between nodes without an
error because the dynamic controls loaded in one node do not match the new
node.
2) A treenode loads content which contains an IE Tabstrip/MultiPage which
contains one or more IE Tabstrip/MultiPage's. The innermost MultiPage
controls do not fire events, no matter what you do.
Has anyone else discovered these flaws in ASP? Were you able to come up
with a workaround? If you ditched the architecture, what did you come up
with?
Have a good one,
Dan
trouble...until now.
What I wanted to do with the new web app was create a single page with a
treenode collection that would dynamically load content into a placeholder.
I ran into two showstoppers:
1)"The control tree into which viewstate is being loaded must match the
control tree"... Meaning that you can't navigate between nodes without an
error because the dynamic controls loaded in one node do not match the new
node.
2) A treenode loads content which contains an IE Tabstrip/MultiPage which
contains one or more IE Tabstrip/MultiPage's. The innermost MultiPage
controls do not fire events, no matter what you do.
Has anyone else discovered these flaws in ASP? Were you able to come up
with a workaround? If you ditched the architecture, what did you come up
with?
Have a good one,
Dan