Archives
-
Url-resolving issue in a "Cacheable-Sharable" UserControl
ResolveUrl and ResolveClientUrl are two methods that help to resolve "~/" prefixed format path to client-browser-usable format. Normally , they take the same effective and just differ in the terminate displaying . Then assuming such a control-holser environment : a UserControl which is designed to shared by a batch of pages; Initially we still find no problems by using either ResolveUrl or ResolveClientUrl to treat url issues in the control , however , if we "cache" the UserControl , mark it with "shared" attribute, and adopt it into an application of multiple pages in different directories , a problem is possible to occur .
-
How to : Dynamically Remove ASP.NET Page Output Cache Entries
I have sought for a perfect solution for a long time and eventually get following old links :