<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Asp.net on Hans Kruse</title><link>https://hanskruse.eu/tags/asp.net/</link><description>Recent content in Asp.net on Hans Kruse</description><generator>Hugo</generator><language>en-GB</language><copyright>© Hans Kruse</copyright><lastBuildDate>Thu, 25 Aug 2016 23:37:43 -0700</lastBuildDate><atom:link href="https://hanskruse.eu/tags/asp.net/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Memoize in ASP.NET</title><link>https://hanskruse.eu/post/2010-06-20-using-memoize-in-aspnet/</link><pubDate>Sun, 20 Jun 2010 02:11:00 -0700</pubDate><guid>https://hanskruse.eu/post/2010-06-20-using-memoize-in-aspnet/</guid><description>&lt;p&gt;I spent quite some time blogging about memoize. Until now I did not have a good solution for Memoize in VB.NET because VB.NET&amp;rsquo;s lambda function is limited to a single expression and VB.NET has no anonymous delegates.&lt;/p&gt;&#10;&lt;p&gt;I first made a Memoize that used a Dictionary. Based on this implementation I made one that wraps the ASP.NET Cache. Certainly some generalisation is possible. I wrote a base class that abstracted away the concrete implementation of the cache using three functions:&lt;/p&gt;</description></item></channel></rss>