blocks|key|1180606|text|我知道这个问题很古老，但为了帮助任何通过搜索找到这个问题的人，值得注意的是，.net+v4为这类场景提供了一个新的通用缓存。它位于System.Runtime.Caching命名空间中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1180607|https://msdn.microsoft.com/en-us/library/dd997357(v=vs.110).aspx|offset|length|1180608|对默认缓存实例的静态引用是:+MemoryCache.Default|1180609|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1S|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

I realize this question is old, but in the interest of helping anyone who finds this via search, its worth noting that .net v4 includes a new general purpose cache for this type of scenario. It's in the System.Runtime.Caching namespace:

<a href="https://msdn.microsoft.com/en-us/library/dd997357(v=vs.110).aspx" rel="nofollow noreferrer">https://msdn.microsoft.com/en-us/library/dd997357(v=vs.110).aspx</a>

The static reference to the default cache instance is: MemoryCache.Default

blocks|key|853296|text|使用HttpRuntime.Cache不存在任何问题。它是一个复杂的内存中哈希表，在web上下文之外非常有用。不过，在一个非Http相关的应用程序中引用HttpRuntime.Cache可能有点代码味道，所以最好将它封装在ICache接口后面，并尽可能地使用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|853297|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There shouldn't be any problem with using HttpRuntime.Cache. It's a sophisticated in-memory hash-table that can be very useful outside of the web context. Still, it might be a bit of a code-smell to reference HttpRuntime.Cache in a non-Http related application, so it can be a good idea to wrap it behind some ICache interface and use that wherever possible.

blocks|key|1180495|text|要记住的一件事是，微软已经发布了一个.NET框架客户端配置文件设置包。这是针对客户端应用程序的3.5框架的一个版本，并且减少了占用空间。客户端配置文件不包括框架的ASP.NET部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1180496|如果应用程序依赖于System.Web，它将阻止应用程序利用客户端配置文件。|1180497|有关更多详细信息，请参阅司各特的博客。|offset|length|1180498|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/scottgu/archive/2008/05/12/visual-studio-2008-and-net-framework-3-5-service-pack-1-beta.aspx^0|0|0|C|6|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

One thing to keep in mind is that Microsoft have a released the .NET Framework Client Profile Setup Package. This is a version of the 3.5 framework that is targeted at client applications and has a reduced footprint. The Client Profile does not include the ASP.NET pieces of the framework.

If your application depends on System.Web it will stop your application being able to take advantage of the Client Profile.

See <a href="http://weblogs.asp.net/scottgu/archive/2008/05/12/visual-studio-2008-and-net-framework-3-5-service-pack-1-beta.aspx" rel="nofollow noreferrer">Scott Gu's Blog</a> for more details.

blocks|key|1180565|text|除了接受Insert()的System.Web.Caching.Cache方法之外，在当前版本的System.Web.Caching.Cache中似乎没有任何依赖于HTTP运行时的东西，所以大部分情况下斯科特是正确的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|1180566|这并不妨碍Microsoft在将来修改类以更好地与HTTP基础结构集成。|1180567|我在另一个答案中写了一个基于WeakReference的轻量级缓存。|1180568|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/15593/practical-use-of-systemweakreference#15616^0|4|8|4|8|0|0|C|L|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|X|8|@]|E|@]|F|$]]|$1|I|3|J|5|6|7|Y|8|@]|E|@$9|Z|A|10|1|11]]|F|$]]|$1|K|3|-4|5|6|7|12|8|@]|E|@]|F|$]]]|L|$M|$5|N|O|P|F|$Q|R]]]]

There doesn't seem to be anything in current versions of System.Web.Caching.Cache that depend on the HTTP runtime except for the <code>Insert()</code> method that accepts a <code>CacheItemUpdateCallback</code>, so Scott is right for the most part.

This doesn't prevent Microsoft from modifying the class in the future to be more integrated with the HTTP infrastructure.

I wrote a <a href="https://stackoverflow.com/questions/15593/practical-use-of-systemweakreference#15616">WeakReference-based lightweight cache</a> in another answer.

blocks|key|1180528|text|不要使用它，即使它确实工作，它也可以在下一个service+/版本中停止工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1180529|当您根据内部实现细节而不是契约(在本例中是MSDN)做一些事情的时候，您可能会在将来遇到麻烦。|1180530|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Don't use it, even if it does work it can stop working in the next service pack/version.

The moment you do something based on internal implementation details and not the contract (in this case, MSDN) you can expect to get into trouble in the future.

blocks|key|181495|text|我曾经使用过它，但是它感觉不对，IIRC大大增加了内存占用。相反，我实现了自己的轻量级缓存机制，这是令人惊讶的容易做到的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181496|它使用了WeakReference类，它允许缓存保持对对象的引用，但也允许垃圾收集器在引用未使用时回收内存。|offset|length|181497|我唯一没有的是一个单独的线程来清理缓存中陈旧的项目。我所做的是，如果缓存中包含>x项，则在添加新项之前，我将遍历所有缓存的项并清除旧项。|181498|如果您需要更健壮的东西，请使用类似于缓存应用程序块之类的工具。|181499|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.weakreference.aspx|1|http://msdn.microsoft.com/en-us/library/cc511588.aspx^0|0|4|D|0|0|0|I|7|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

I once used it, but it didn't feel right and IIRC increased the memory footprint quite dramatically. Instead, I implemented my own lightweight cache mechanism which is surprisingly easy to do. 

It utilized the <a href="http://msdn.microsoft.com/en-us/library/system.weakreference.aspx" rel="nofollow noreferrer">WeakReference</a> class which allowed the cache to keep references to the object, but also allows the Garbage Collector to reclaim the memory if the reference is unused.

The only thing I didn't have was a separate thread to clean up stale items in the cache. What I did do is if the cache had > x items in it, I would go through all the cached items and turf out the old items before adding the new item.

If you need something more robust, use something like the MS Enterprise Library <a href="http://msdn.microsoft.com/en-us/library/cc511588.aspx" rel="nofollow noreferrer">Caching Application Block</a>.

blocks|key|1180665|text|如果您正在寻找一个通用解决方案:这是依赖注入方法的典型情况。使用这种方法，您可以跟踪Scott、和+MSDN！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1180666|在库中没有System.Web引用的情况下注入类似于HttpRuntime.Cache的System.Web依赖项。|1180667|entityMap^0|1C|1|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

If you are looking for a general solution: This is a typical situation for the dependency injection approach. Using this approach you can follow Scott Hanselman and MSDN!

Inject a System.Web dependency like HttpRuntime.Cache without having a System.Web reference in your library.

blocks|key|1180478|text|为什么不完全回避这个问题并使用企业图书馆的缓存块呢？你可以使用System.Web.Caching，但如果遇到问题，你可能得不到微软的支持，你会扬眉吐气，所以这可能不值得。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1180479|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/cc511588.aspx^0|F|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Why not avoid the question completely and use the <a href="http://msdn.microsoft.com/en-us/library/cc511588.aspx" rel="nofollow noreferrer">Caching Block of Enterprise Library</a>? You could use the System.Web.Caching, but you probably won't get Microsoft support if you run into issues and you'll raise eyebrows so it might not be worth it.

Scott Hanselman <a href="http://www.hanselman.com/blog/UsingTheASPNETCacheOutsideOfASPNET.aspx" rel="noreferrer">says yes</a>.

<blockquote>
 Adding System.Web to your non-web project is a good way to get folks to panic. Another is adding a reference to Microsoft.VisualBasic in a C# application. Both are reasonable and darned useful things to do, though.
</blockquote>

MSDN <a href="http://msdn.microsoft.com/en-us/library/system.web.caching.cache.aspx" rel="noreferrer">says no</a>.

<blockquote>
 The Cache class is not intended for use outside of ASP.NET applications. It was designed and tested for use in ASP.NET to provide caching for Web applications. In other types of applications, such as console applications or Windows Forms applications, ASP.NET caching might not work correctly.
</blockquote>

So what should I think?

Is it OK to use HttpRuntime.Cache outside ASP.NET applications?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

作者: Scott 。将System.Web添加到非web项目是一种让人们恐慌的好方法。另一个是在Microsoft.VisualBasic应用程序中添加对C#的引用。不过，两者都是合理的，也是非常有用的。MSDN .缓存类不适合在ASP.NET应用程序之外使用。它是为在ASP.NET中使用来为Web应用程序提供缓存而设计和测试的。在其他类型的应用程序中，例如控制台应用程序或Windows应用程序

问在HttpRuntime.Cache应用程序之外使用ASP.NET可以吗？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在HttpRuntime.Cache应用程序之外使用ASP.NET可以吗？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在HttpRuntime.Cache应用程序之外使用ASP.NET可以吗？
EN