has controlling httpruntime.cache altered asp.net mvc?

so, i looking over customary cache concentration scheming section exam controller thought, hey, accessing httpruntime.cache directly deliberate pernicious mvc?

i hang cache surrogate category implements cache-like interface (tho many simpler) i ridicule during tests. nonetheless i'm wondering that's already finished me new framework. i can't anything, however.

here's an thought i it:

public actionresult dostufflol(guid id)
{
  var denote = cacheutil.getorcreateandstore(
                  "dostufflolmodel",
                  () =>
                  {
                    /* make denote here; radical things */
                    relapse model;
                  });
  relapse view("dostufflol", model);
}

so, aged patterns accessing cache changed? there any improved patterns caching movement law mvc?