[RESOLVED] IIS Caching? (Local)

I know this does not belong in the asp.net section, but seeing you guys will be using IIS and the PHP guys wont.

I removed Apache on my machine and now only use IIS. Had the web platform installer help me get wordpress, php, mysql working as well. (Do both php and asp.net)

All works fine as before, but I just find my pages get cached somewhere (assume by IIS?) now, making it a pain to write html/css. Have to do hard refresh'es over and over before some changes get picked up.

Any advice? Been ages since I actually used IIS (now 7, but last I used was 5 I think)

It sounds like the browser caching static files (html, css, JS). When in testing faze it can be painful but you need to keep clicking the refresh button to get these static files from the server (local or remote) instead of from the temp files used locally (the client machine) by the browser.

If your talking abour dynamic pages - aspx then you can set caching properties to server them every time from the server.

Hmmm...how annoying. Spending more time on re-freshening than tweaking my css here.

But then...this was not an issue until yesterday when I still used Apache. Isn't there something in IIS one can turn off (I did unchecked the performance caching options)

This also seems to have no effect (figured might be a short term solution)
<meta http-equiv="Cache-Control" content="no-cache"/>

I have not tried it but I opened IIS on my local machine and under http headers you can set content expiration to imediate. I don't know what effect that would have on include files like css. I tend to leave IIS config the same as the remote server so I just click refresh.

Maybe someone else knows more - It's dinner time so I've got to go but am interested what other replies you get.

Opened my eyes and saw a big clear icon in IIS manager with an "Output Caching" caption.
Double-Click it, and click "Edit Feuture Settings" in the right pane. Now just turn off caching.
Retarded I am!

Hey,

Just on a side note, while I am testing html/css, I typically always hold down CTRL and hit Refresh, that way ensuring the browser requests a new version of the page.

Just a habit I have gotten into.

Gary

Yep...hard refresh is what I resort too also (though I still need to do that several times, driving me nuts)

Thing with hard refresh is just it reload all your css/javascript/images. Not always that great on a development machine.

Spoke too fast about fixing it. Posted over on the PHP section about WIMP problems.