How to remove Child action cache about mvcdonutcaching HOT 5 CLOSED

Finally found the solution. The area is ignored in the url for removing the child action. This is different then the default OutputCache attribute. I think this is a bug?

So the solution is:

cacheManager.RemoveItem("News", "LastArticles", new { numberOfArticles = 2 });

See for more information this StackOverlow question.

from mvcdonutcaching.

Thanks for reporting, I know exactly what happens.
When generating the cache key during action invocation, the default keybuilder only builds an area key component if the area is not null or empty.
By calling RemoveItem[s] with an area component set to empty, the area key component shouldn't be built either, otherwise no key will match for removal

from mvcdonutcaching.

Thank you for your reply.
So if I understand it right, this is by design? Does this effect other NewsControllers with Action LastArticles in other Area's?

from mvcdonutcaching.

Nope this is a bug, the area part should be ignored if empty for removal action.
Thus, the normal behaviour would be to remove the area impacted keys. This is what you are doing by calling cacheManager.RemoveItem("News", "LastArticles", new { numberOfArticles = 2 });

Generally speaking it's a bad idea to have controllers with the same name in different areas, we got problems in the past with that (not related to DonutCaching).
The solution we adopted was to prefix our area controllers with the area name itself, making url routing tweaks afterwards to hide the redundancy.

eg NewsController and AdminNewsController in the Admin area + route tweaks to avoid /Admin/AdminNews and have /Admin/News routes instead.

from mvcdonutcaching.

Well it's working for now with a workaround so no critical bug :).
Thanks for the feedback.

from mvcdonutcaching.