Question

I have a web user control, it serves some potentially intensive data calculations and I would like it to be output cached so that each page view doesn’t recalculate the data. It resides on very frequently viewed pages so it’s quite important I get it working right!

For context, it’s used on our arcade:
http://www.scirra.com/arcade/action/93/8-bits-runner

Click on stats, the data for the graphs and stats are generated from this webusercontrol.

The start of the control is as follows:

public partial class Controls_Arcade_Data_ArcadeChartData : System.Web.UI.UserControl
{
    public int GameID { get; set; }
    public Arcade.ChartDataType.ChartType Type { get; set; }

    protected void Page_Load(object sender, EventArgs e)
    {

Now the difficulty I’m having is the output cache needs to be dependant on both the GamID and the ChartType.

This control is re-used with many different combinations of GameID’s and Types, I need it to create a cache for each of these but am struggling to find out how to do this.

For example, one arcade game might pass in GameID = 93 and Type = GraphData, another might be GameID = 41 and Type = TotalPlaysData and another might be GameID = 93 but Type = TotalPlaysData. These should all return different data and have different output caches.

The control is used on the games page sort of like this (the parameters are actually set in the codebehind)

<div>Total Plays:</div>
<div class="count"><Scirra:ArcadeChartData runat="server" GameID="93" Type="TotalPlays" /></div>
<br /><br />
<div>Total Guest Plays:</div>
<div class="count"><Scirra:ArcadeChartData runat="server" GameID="93" Type="TotalGuestPlays" /></div>

etc.

Any help appreciated! I’ve spent a while looking online and it’s kept coming up as something I need to solve but can’t figure this one out.

Edit

Edit: I’ve tried adding this line to my control:
<%@ OutputCache Duration=”20″ VaryByControl=”GameID;Type” %>

But it just throws the error Object reference not set to an instance of an object. on the line where GameID is being set for the first time on the ASPX page using the control.

Answer 1

When a Control is retrieved from the output cache, it’s not instantiated as an instance that you can manipulate; you just get the output the Control generated, not the Control itself. For example, you can’t set properties on a cached Control from code behind, as you said in your question. The vary-by properties should be set declaratively (using an ExpressionBuilder might also work, though I haven’t tried it).

To see in code behind whether a control has been retrieved from the output cache, check for null:

if (this.YourControlID != null) // true if not from cache
{
    // do stuff
}

Even with that caveat, Control output caching is a bit quirky.

Try this:

<%@ OutputCache Duration="20" VaryByControl="GameID;Type" Shared="true" %>

The output of the Control is stored in the output cache by associating it with a certain key. With Shared="true", the cache key is the value of all specified properties, together with the Control’s ID. Without Shared="true", the cache key also includes the Page type, so the output would vary by Page — which doesn’t sound like what you want.

If you use the Control on more than one page, be sure to use the same ID on each page if you can, since the ID is included as part of the key for the output cache. If you can’t or don’t use different IDs, you will get a new copy of the Control’s output in the cache for each unique ID. If the Controls with different IDs always have different property values anyway, that may not be an issue.

As an alternative to the OutputCache directive, you can set an attribute on the class declaration:

[PartialCaching(20, null, "GameID;Type", null, true)]
public partial class Controls_Arcade_Data_ArcadeChartData : UserControl