This is an important point if using MiniProfiler in production. As if the first visit to a page is by a user where MiniProfiler is enabled, all subsequent requests will include the MiniProfiler results in the DOM (as they are now cached). Not only will the results be incorrect (as they only consider first load), but all visitors will be able to see your MiniProfiler results.
Firstly, to enable donut hole caching, I'm making use of:
http://mvcdonutcaching.codeplex.com/
This allows you to add actions which will not be cached when using the OutputCache.
Given the above, you can remove @using StackExchange.Profiling;
from your Layout page. You can then replace:
@MiniProfiler.RenderIncludes()
With:
@Html.Action("MiniProfiler", "DoNotCache", excludeFromParentCache: true)
I have created a DoNotCache controller, so all my non-cacheable elements are together, but this is not required and you can place this action in any controller.
public ActionResult MiniProfiler()
{
return View();
}
And then the view itself just looks like:
@using StackExchange.Profiling;
@{
Layout = null;
}
@MiniProfiler.RenderIncludes()
This will ensure the MiniProfiler results are displayed when appropriate, and not cached in production even in places where you use the DonutOutputCache
annotation.