Thanks, good to know.
Can you customise how the cache key is generated or does it always use the whole dto?
Is the existing method being obsoleted?
Will the existing methods have the same ability (informing client of maxage)?
A weakness in the .net cache attribute (or attributes in general) is that you end up using string literals to express things that needn’t or shouldn’t be strings (i.e. varyByParam and property names) as they don’t support expressions/funcs/delegates so normally try and avoid this kind of thing. Not as refactor friendly and more prone to runtime errors.