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 a CSS page though, it will be ignored because, by default, CSS pages are not processed by ASP.NET. On the whole, I wouldn't waste any more time fretting over it. This is only something minor that occurs in design-time and not something that will affect end users of your app (how often will you be changing the CSS when they start using it?). Cheers, Duncan Smart [EMAIL PROTECTED] On Mon, 22 Apr 2002 12:58:36 +0530, LeTS <[EMAIL PROTECTED]> wrote: >Hi, > When we change the Style Sheet properties linked to a page the >changes are not getting effected in the Design View. This gets effected if >we close the MS VStudio .net Environment and open it again. >Again, once we change the stylesheets, the browser is taking the cached one, >hence the changes are not seen when viewed on the browser - this I guess is >a problem with respect to caching. What is the alternative syntax for ><%Response.Expires = -1%> in Dotnet (this works fine with the prev. version >of ASP) > >regds, >Sendhil. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
