I was playing with the new beta of Ext JS 4 the other day and noticed that sometimes the scripts were being cached, so my changes weren’t taking effect. Initially I thought this was because I’d upgraded to Firefox 4 – I use the Web Developer add-on which allows me to disable browser caching, and I’d assumed the cache setting had reverted when I upgraded. However the cache was indeed disabled, so I had to dig a little deeper.
- Open up IIS Manager
- Optionally select the site you’re working with
- Open the ‘Output Caching’ module
- Select ‘Add…’ from the right hand menu
- Enter a file extension of ‘.js’ and disable both user-mode and kernel-mode caching, click OK.
According to the IIS blog IIS should flush the cache when files are modified; however this wasn’t the behaviour that I was seeing. I had to completely disable caching to guarantee file modifications made it to the browser.