Hello,

I have been using the CacheItemRemovedCallback to trap each time an
object is released from the cache. I have also set up
dependencies(directory and cachekeys). With the identical code base
deployed to my local Windows XP box and a Windows 2003 server, I notice
two different behaviors.
1. On the Windows XP box, when an item is removed and has dependencies,
the original item and each of the dependant items will cause the
delegate to fire. All of the relevant items are removed from the cache
based on the dependencies.

2. On the Windows 2003 server, when the same item is removed and has
the same dependencies, only the original item being removed fires the
delegate. All of the relevant items are removed from the cache based on
the dependencies.

Can anyone explain why this might behave differently on the two
systems?

Thanks in advance,
Shawn

There's something fishy with the cache, please see if this can help you...

http://msdn.microsoft.com/newsgroups...33e&sloc=en-us

"Shawn" wrote: