Hey everyone,
I am curious what the performance impact of a custom control would be if it
had a significant hierarchy of children. For example, 40 child controls, 5
levels deep, each control on average has 20 properties. What would be the
best way to implement such a thing?
The book I am reading uses templated controls and basically reconstructs the
entire hierarchy everytime page is accessed based on the tags in the .aspx
file, but books example only has 2 child controls. Would it make sence to
use xml configuration file instead of template elements? Would it be
possible to read the xml file once, build the hierarchy and then save it
somewhere, so that it is only regenerated when xml file changes? I was
thinking taking the root element and storing it in application cache, or
even serializing it to disk, but I am not sure if controls are allowed to be
reused for subsequent requests.
So anyone know the proper way such situation would be handled?
Oh yeah, I was thinking placing the whole thing into a user control and
making it cachable, but control would still be regenerated if it has to
process post-back events, right?
Thanks for any info
-- Dennis