mvcdonutcaching | NET MVC Extensible Donut Caching brings donut | Caching library

by moonpyk C# Version: v1.3.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | mvcdonutcaching Summary

mvcdonutcaching is a C# library typically used in Server, Caching, Angular applications. mvcdonutcaching has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

ASP.NET MVC Extensible Donut Caching brings donut caching to ASP.NET MVC 3 and later. The code allows you to cache all of your page apart from one or more Html.Actions which can be executed every request. Perfect for user specific content.

Support

Quality

Security

License

Reuse

Support

mvcdonutcaching has a low active ecosystem.

It has 146 star(s) with 47 fork(s). There are 16 watchers for this library.

It had no major release in the last 12 months.

There are 29 open issues and 29 have been closed. On average issues are closed in 67 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of mvcdonutcaching is v1.3.0

Quality

mvcdonutcaching has 0 bugs and 0 code smells.

Security

mvcdonutcaching has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

mvcdonutcaching code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

mvcdonutcaching is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

mvcdonutcaching releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

mvcdonutcaching saves you 309 person hours of effort in developing the same functionality from scratch.

It has 743 lines of code, 0 functions and 66 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of mvcdonutcaching

Get all kandi verified functions for this library.

mvcdonutcaching Key Features

No Key Features are available at this moment for mvcdonutcaching.

mvcdonutcaching Examples and Code Snippets

No Code Snippets are available at this moment for mvcdonutcaching.

Community Discussions

Trending Discussions on mvcdonutcaching

How to pull a ViewComponent outside a response cached controller's action in ASP.NET Core

MVCDonutCaching failing when using custom Redis output cache provider

QUESTION

How to pull a ViewComponent outside a response cached controller's action in ASP.NET Core

Asked 2020-May-15 at 01:25

For performance purposes, I need to cache the results of the homepage action, while allowing the display name of the logged-in user to remain uncached.

I used to achieve something similar on ASP.NET MVC Framework projects using DonutOutputCache. This system was very useful because you were able to put an entire action into the output cache while maintaining partial view results outside of the cache. I could thus have three or four partials who needed personalization—e.g., a survey, an analytic tag, the user name and avatar, a behavior based article list, etc.).

Do you know if I could handle this with ASP.NET Core's new [OutputCache] attribute or Tag Helper?

At the moment, I put the whole home page into a classic memory cache. It would be fantastic to have this kind of Tag Helper:

...

ANSWER

Answered 2018-Nov-21 at 14:10

I'm not sure about what you were using previously, but I don't think it was actually doing what you think. The whole point of an output cache is bypassing the view rendering process, as such, whatever you cache is just returned as-is, not further processed to determine if something inside needs to be rendered.

If you cache your entire page, then you cannot have any part inside that needs to vary per user. You'll simply need to reduce the scope of what you're caching. Cache the parts of the page that don't vary, and that will at least give the main page a leg up in rendering. This is what the cache tag helper is for. You can also cache just for a particular user with this tag helper:

Source https://stackoverflow.com/questions/53412902

QUESTION

MVCDonutCaching failing when using custom Redis output cache provider

Asked 2019-May-30 at 16:09

I have the following custom Redis output cache:

...

ANSWER

Answered 2019-May-30 at 16:09

Ok the reason why the getType was returning null is because the nuget package is done in .net4 and the project using it was .net4.6.1 and therefore the nuget package was unable to get the type because the class was incompatible. As I had the source, I was able to create a custom redis provider in the source solution and just point my project and web config at the updated output

Source https://stackoverflow.com/questions/56379793

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install mvcdonutcaching

The best way to add donut caching to your MVC project is to use the NuGet package. From within Visual Studio, select Tools | Library Package Manager and then choose either Package Manager Console or Manage NuGet Packages. Via the console, just type install-package MvcDonutCaching and hit return. From the GUI, just search for MvcDonutCaching and click the install button.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: