Bug in the CacheDependency or Cache object? Help!

[Dave]

Using ASP.Net 2.0 on Vista with IIS6, if I set a CacheDependency on a file
into a Cache entry that I insert and then delete a subdirectory in the same
directory that the file is located in then my dependency is triggered and my
cache object is deleted.

If I create a directory or delete another file in that same directory then
the Cache is not bothered.

My CacheDependency specifies the full and proper file name and not just the
directory path.

Is this a known problem?

Fix or workaround?

Thanks,
Dave at DotNetCodeSlingers dot com

 

[Dave]

Anone had this problem? Please try to see if get similar results. Could be
easily tested in some current asp.net 3.0 app just by deleting a directory.

Thanks for any feedback,
Dave

 

[Dave]

Got this working by discreetly deleting the files in a parallel directory
rather than recreating the directory but then caching broke again if I write
a file into a sub sub directory from the root directory. Sort of like
caching is dependent on the entire directory tree CONTAINING the dependent
file rather than just the file itself.

Would love MSFT or anyone to comment on this please.

Is this a bug or expected behaviour. Is there a workaround?

Thanks,
Dave

 

[Dave]

Well I found another workaround for the 2nd problem by writing into a directory parallel to the dependent file which was in the website root. The 2nd problem seems to be that I could not write a file into a subdir of the \bin directory without blowing the Cache objects that were dependent upon a file in the website root.

So in summary there is a bug in CacheDependency when used with Cache for a dependent file in the website roor that deletes the cached item if:
a.. writing data to a file in a subdir of the \bin directory
b.. deleting and creating a directory that is parallel to the dependent file
Would be great if anyone could verify this or if MSFT would fix! Don't think it is my imagination run wild...

Thanks,
Dave