Sendhil,
Client-side caching ultimately is decided by the client. Design View does
seem to have these glitches. I have found that closing the document in VS,
previewing in IE (do a shift-F5 to refresh if necessary), and then opening
it in VS again gets around it.
If you put "Response.Expires" in
>What is the alternative syntax for
><%Response.Expires = -1%> in Dotnet (this works fine with the prev. version
>of ASP)
You could try:
Response.Cache.SetNoServerCaching()
Response.Cache.SetNoStore()
Response.Cache.SetRevalidation(HttpCacheRevalidation.AllCaches)
Response.Cache.SetMaxAge(System
