>I was getting the same problem myself when FireFox (and even IE) would remember the previous version of the script and would not want to refresh with the newer versions.
>

Good thought. Yes, the browser can (and will) cache external JS files. Usually doing a CTRL-F5 will force it to refresh, but in some cases I've seen it still use the cached copy. FF is pretty aggressive when it comes to caching that stuff. It can be even worse if you deploy something and then need to make a change to the JS file. I normally set a long expiration on JS and image files from within IIS to keep from having to serve them up all the time, so even if you make changes it could still be cached on the client for a while before it gets updated. A lot of places will change the filename (ex. prefix the file with the last update date and/or time) and change the reference in your code to make sure they get the correct version.