title: Autoversioning CSS/JS in ASP.NET MVC?
body: <p>So I was reading <a href="https://stackoverflow.com/questions/4841455/auto-versioning-in-asp-net-mvc-for-css-js-files">this stackoverflow post</a> about "autoversioning" in ASP.NET MVC for CSS/JS files and was wondering what the "best" strategy is to do this.</p>
  
  <p>The solution provided inserts an assembly number - which means everytime you publish - it will change EVERY SINGLE file which is <em>not ideal</em> because if you make modifications to just 1 *.css or *.js then it will change each and every file.</p>
  
  <p>1) How can it be done just for "single files" instead of using site wide assembly using modification date or something on IIS7 ?</p>
  
  <p>2) Also if I have some sort of "static" asset like - <a href="http://static.domain.com/js/123.js" rel="noreferrer">http://static.domain.com/js/123.js</a> - how can I use rewrite to send the latest file for a request if someone has integrated this static link onto their site ?</p>
  
  <p>i.e. <a href="http://static.domain.com/js/123.js" rel="noreferrer">http://static.domain.com/js/123.js</a> is the link and when a request comes for this - check and send latest file ?</p>