We have faced a problem on one of our production sites. JavaScript file was updated for a page and uploaded to IIS. We directly include file using \[code\]<script src="http://stackoverflow.com/questions/15717618/PATH_TO_SCRIPT" type="text/javascript"></script>\[/code\]We started receiving complaints from clients that the page is broken. It was happening as the JS file was cached on client machines and was not refreshed from server.How can we avoid this kind of scenarios without changing javascript file name in future?ASP.Net bundling and minification might be helpful. But there are lot of pages and site is quite legacy. Almost all the pages have some heavy logic written in associated js file.The site is running .Net 4.0 and IIS 7