The person in that post is using a third-party library to implement donut caching (I don't think it is supported natively but I might be wrong). Different libraries will have different implementation techniques, some much use new attributes, some might use parameters on helper methods etc. Just pick a library that does what you need and follow its implementation instructions.
Don't confuse yourself with the naming. Donut Hole Caching is a server-side caching technique in which the some portion of tge page is cached.
The tools for implementing donut hole caching are relatively simple: You just need the HtmlHelper’s Action method and Partial Views. In the context of ASP.NET, you can implement the "donut caching" technique using a combination of ChildActionOnly and OutputCache attributes.
So the following code is actually implemeting a donut hole caching technique:
I've read about it but I haven't done any hands-on coding with it. It seems interesting to me and I'd like to try it out. I'll give you an update or perhaps make an article about it after trying it out.
I tried the getting started but all I got was a white page, with the <Router> tag in it, i.e. did not execute / expand to the full page with page content ...
I guess I will try again with 0.4 ...
Despite that, I'd say it looks promising!
And... it's now working!
Everything else looks pretty slick yet obvious (for an MVVM, and VueJS addict that I am)!
For example, you can order dishes on handheld devices that run on your Iphone, Androi, winphone, restaurant, coffee shop, and so on. Any programming language that runs on the above devices, for example simple you have to share yourself with.