travisbrown
Technical User
- Dec 31, 2001
- 1,016
We are getting this incredibly frustrating issue with IIS serving what seem to be cached files on our development machine.
Say we make a change to a javascript file, or delete the file entirely, the server keeps serving up the original file. Seemingly the only way to rectify the issue is stop and restart the IIS service for that website.
I know this isn't a browser caching issue because even moving to a "virgin" machine that hasn't previously visited the site demonstrates the issue.
What's the way around this?
Say we make a change to a javascript file, or delete the file entirely, the server keeps serving up the original file. Seemingly the only way to rectify the issue is stop and restart the IIS service for that website.
I know this isn't a browser caching issue because even moving to a "virgin" machine that hasn't previously visited the site demonstrates the issue.
What's the way around this?
