That was already suggested over a year ago, the topic has since changed to a request about why HtmlAnchor acts like this.. but yes caching asp.net controls isn't suggested, theres potentially a lot of complex interactions with context that can go wrong given
that controls can do absolutely anything.. and then theres weird bugs like this..
J, I definitely wasn't suggesting that anyone caches control instances. I was just interested in why this bug occurs. More to the point, why this bug still occurs in