Hi,
If it is ASP.NET 2.0 then you should not have much probelm.There is now new
feature in ASP.NET 2.0 whereby you can save page output cache even to hard
disk.This is what one documentation has to say on Disk Otput Cache:
Caching to Disk
ASP.NET 2.0 has the ability to save cached responses in memory and to disk.
The benefit of storing a cached item on disk is that even if it’s removed
from memory to ensure performance or because the web application was
restarted or the application domain was recycled, the cached item remains
available (although it’s slightly more expensive to retrieve). Of course,
cached items are removed both from memory and disk when they expire.
Essentially, disk caching allows ASP.NET to cache a much larger amount of
data. Disk caching is enabled by default, and every web application is
allocated 2 MB of space. However, you can configure the maximum size to use
for disk caching and the location where cache information is stored using the
web.config file. Here’s an example that sets a maximum 20 MB disk cache:
<configuration>
<system.web>
<caching>
<outputCache>
<diskCache maxSizePerApp="20" />
</outputCache>
</caching>
</system.web>
....
</configuration>
You can also disable disk caching altogether by supplying the enabled
attribute and setting it to false or by changing the path where cached
information is stored using the path attribute.
Finally, you can choose to create pages that opt out of disk caching
altogether using the Disk- Cacheable attribute in the OutputCache directive
(or the diskCacheable attribute in the cache profile that’s defined in the
web.config file).
<%@ OutputCache Duration="20" VaryByParam="None"
DiskCacheable="False" %>
Thanks and Regards,
Manish Bafna.
MCP and MCTS