J
jason
I've seen a few designs where developers condition dynamic web control
on the same page, enabling/disabling/visible=true/false using viewstate
and postback information to drive what the page does vs. a building
static pages for possible outcomes that call each other.
In terms of ease of support and troubleshooting, which is a generally
viewed as a better design? and why?
Also, wanted to ask, are session variables still the best way to
communicate control selections between pages? I'm asking because I've
seen a few professionaly developed solutions where they do not even
appear to be using session variables.
On the subject, is it true that setting of session variables is
something that must be done via code and that (or at leaste it appears)
cannot be done when the control is configured graphically. I noticed
that you can pass datasources values from other controls, but they
appear to be available only from the current page. Is this one reasons
for trying to make pages as self contained and dynamic as possible?
Can anybody point to any small/simple intranet type sample asp.net ap
with sources that demonstrates good asp.net design and viewstate
management?
on the same page, enabling/disabling/visible=true/false using viewstate
and postback information to drive what the page does vs. a building
static pages for possible outcomes that call each other.
In terms of ease of support and troubleshooting, which is a generally
viewed as a better design? and why?
Also, wanted to ask, are session variables still the best way to
communicate control selections between pages? I'm asking because I've
seen a few professionaly developed solutions where they do not even
appear to be using session variables.
On the subject, is it true that setting of session variables is
something that must be done via code and that (or at leaste it appears)
cannot be done when the control is configured graphically. I noticed
that you can pass datasources values from other controls, but they
appear to be available only from the current page. Is this one reasons
for trying to make pages as self contained and dynamic as possible?
Can anybody point to any small/simple intranet type sample asp.net ap
with sources that demonstrates good asp.net design and viewstate
management?