njapp said:
stevo_ said:
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 3.5 SP1
no sane person will cache an entire control, it just doesn't makes sense, they should trow an exception if someone is trying to push a Control in Cache, how is that for a fix? Tongue Out we now have .NET source code you could debug and see what's up