D
Doug
Looking for opinions/suggestions:
Suppose I have a "region" of an aspx page I want to hide or show based on
whatever runtime conditions. Additionally, the entire region is defined by
an HTML <TABLE>. There is nothing else in the region beyond whatever is
contained in the <TABLE>.
I see at least two options for showing/hiding this region.
1. Wrap the table in an <ASPanel> and set the panel's Visible property to
show or hide the region (I've done this and it works fine - just have to be
mindful of the Panel's EnableViewState setting depending on what other
controls exist in the region).
2. Define the <Table> With Runat=Server so I can access it's properties from
the code-behind; then set it's Visible property to show or hide the region
(I've never actually done this so I don't know if it would even work).
In any case - which would be better between these alternatives? Any
additional alternatives? Rationalle for making a choice?
Thanks.
Suppose I have a "region" of an aspx page I want to hide or show based on
whatever runtime conditions. Additionally, the entire region is defined by
an HTML <TABLE>. There is nothing else in the region beyond whatever is
contained in the <TABLE>.
I see at least two options for showing/hiding this region.
1. Wrap the table in an <ASPanel> and set the panel's Visible property to
show or hide the region (I've done this and it works fine - just have to be
mindful of the Panel's EnableViewState setting depending on what other
controls exist in the region).
2. Define the <Table> With Runat=Server so I can access it's properties from
the code-behind; then set it's Visible property to show or hide the region
(I've never actually done this so I don't know if it would even work).
In any case - which would be better between these alternatives? Any
additional alternatives? Rationalle for making a choice?
Thanks.