The location of where the cache is stored is determined by Location property of the OutputCacheAttribute. For instance you can set Location=OutputCacheLocation.Client so it will keep the cache on the client browser.
The documentation of the OutputCacheLocation enumeration type contains the possible values:
i guess client side caching will not give much benefit....am i right?
Of course, Output caching provides you with a very easy method of dramatically improving the performance of your ASP.NET MVC applications.
#1 - There doesn't seem to be a question here.
#2 - This sounds like a homework assignment, no one is going to do your work
#3 - Tell / show us what you have done and the community will be glad to help out.
it is not a assignment
it is one type of challenge to binding data in one grid-view with 2 different control..
the qus is if 1st page load the data can be bind at page load and then i select data like one dropdown and one text box in dropdown any value i select and text box those value selected value comes on selected dropdown list the i hit search data can bind in gride view
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)!