Actually, I had that annoying problem happen today. A reboot fixed it. I
believe it boils down to the dll must be older (or younger i forget which
one) than the source files. In any case, the cached files are stored in the
temp ASP.NET working folder. So you can purge those instead of rebooting.
--
Regards,
Alvin Bruney - ASP.NET MVP
[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @
www.lulu.com/owc, Amazon.com etc
"Donal McWeeney" <macker (AT) newsgroup (DOT) nospam> wrote
Quote:
Hi,
We have one dev box here (Win2003 server/Sharepoint/Visual Studio 2003)
that is showing some funny issues ... with what appears to be the asp.net
page caching.
What appears to happen is that when you do a get latest version of the
page from sourcesafe, (or sometimes edit/save a page) the old page still
seems to be running from the asp.net cache. IISRESET does not seem to even
fix the problem when this happens. The way to fix the page is to make a
few changes, F5 in the browser and then undo checkout. Not very ideal.
Any ideas how to resolve this. Or examine the page cache to see if this is
the case. Or manually purge the cache.
Thanks
Donal |