I am using the PartialCaching attribute on the base class of a user control.
I would like the cached controls to vary based on the properties set on the control instance.
For example:
<mycontrols:control1 runat="server" param1="10" param2="20" />
...output would be cached separately from a control instance with different properties:
<mycontrols:control1 runat="server" param1="15" param2="20" />
...and this control would be cached separately as well:
<mycontrols:control1 runat="server" param1="10" param2="25" />
However, if two control instances on two separate pages had identical param1 and param2 properties, I'd like them to cache as one object (so that cached control would be shared).
Can the above use case be achieved with PartialCaching attribute? What settings would I use? varyByControl?
Also, is it possible to make the cache duration variable at runtime?
Thanks.
To answer your first Q, let me first tell you that your question itself has the answer ;). 'Shared' ... yes that's the keyword :) To have a single instance in cache for the user control across all the pages, set Shared='true' in the @OutputCache directive. This should be set at the user control level i.e. in the ascx page.
To cache the user control based on user control properties, you should specify the fully qualified name of the properties in the varyByControls section of the PartialCachingAttribute. Multiple properties if any should be separated by semi-colons.
or you can also include the PartialCache attribute for the user control:
OR another way to cache the control on the combination of both values would be:
The last parameter (true) specifies shared. Duration is specified by 60. Refer to the link How to: Cache Multiple Versions of a User Control Based on Parameters
To answer your second Q, to make the cache duration for the user control variable at run time, you can do it in two ways:
Assign it in the user control code behind:
You can assign it in the code behind of the page where user control is referenced using the ID of the user control.
e.g. If the user control on the aspx is:
then in the code behind of aspx, you should write:
FYI, if both the user control and page are cached: If the page output cache duration is less than that of a user control, the user control will be cached until its duration has expired, even after the remainder of the page is regenerated for a request. For example, if page output caching is set to 50 seconds and the user control's output caching is set to 100 seconds, the user control expires once for every two times the rest of the page expires.
What you need is Caching Multiple Versions of a User Control by Using Declarative Attributes.
I'm posting a new answer to this very old question because the accepted answer is woefully inaccurate. This correct answer is:
I blogged about this recently right here: http://tabeokatech.blogspot.be/2014/09/outputcache-on-user-controls.html .
A way you could make this work is call the builder method for the PartialCachingControl yourself in code-behind, and embed the property value you want to vary by in the guid parameter:
That neatly takes care of varying caching duration in code-behind as well. Make sure you remove the OutputCache directive from the markup in the ascx though when you do this. Otherwise the LoadControl gets you another PartialCachingControl and the cast fails.