title: Should we deploy scrrun.dll (Windows Scripting Runtime)?
body: <p>Our VB6 application relies heavily on the use of scrrun.dll (Windows Scripting Host). Until a year ago we used to deploy this dll with our installer. <a href="http://en.wikipedia.org/wiki/Windows_Script_Host" rel="nofollow">Since the Windows Scripitng Host is supposed to be part of Windows</a> we removed the dll from the installation package. However, now and then surface customers who have a non functional scrrun.dll on their system and we have to help them reinstall or reregister it.</p>
  
  <p>So, should we put the scrrun.dll back in the installation package? Should we perform some check on installation? Or should we just live with the fact that we have to provide hands on support to some of our customers to set their systems right?</p>