There is a known issue with using output caching on aspx pages that send back where Asp.Net returns the cached page, instead doing the reverse logic
I came across what seems like an elegant solution here
However, this does not seem to work when output caching occurs in the user control, and not on the page.
Can anyone suggest a workaround? Or am I missing something
Thank.
source
share