This rule kicks off due to all the Protected members added to a class
derived from Page. When you drag a textbox to the designer, you get a
Protected variable declaration. This is necessary, as the ASP output
is an instance of your page derived class at runtime and must interact
with these objects.
How do we deal with this?
The FXCOP says :
"Use properties instead. They do not compromise usability or
performance and they do provide flexibility in that they conceal the
implementation details of the underlying data."
This does not seem to be possible in between the rendering of the page
and its codebehind?
Brian
