As mentioned <a href="https://stackoverflow.com/questions/1361501/where-does-msscript-ocx-gets-installed-from" rel="nofollow">here</a>, this component became a part of the windows operating system. However VB6 runtime may not be supported on Windows 8 and beyond. So I'm afraid this component may be going away too (even tho it is a part of windows OS). We are going to be attempting to utilize it via a C# consumer using Interop.MSScriptControl.dll, very soon. I've even seen some folks have issues with it on <a href="https://stackoverflow.com/questions/1215867/what-replacements-are-available-for-vbscript-in-an-application" rel="nofollow">Windows7</a>. Has anyone had success running it on Windows 7 and Windows Server 2008 R2? Does anyone think it will still work on Windows 8? Currently compiling for x86 32-bit CPU with thought that 64 bit system would use WoW64 to use it. Thanks!Answer1:
The ScriptControl (msscript.ocx) is specific to 32bit Windows and is specific to older languages that cannot interact with the CLR/.Net. It continues to exist on Windows 7 in C:\Windows\System32 for 32bit and C:\Windows\SysWOW64 for 64bit. With Microsoft slowly phasing out 32bit portions of the Windows OS, this will eventually go away, too. When that may happen is anyone's guess, though.
There is a .Net equivalent though that can be used in 32bit and 64bit flavors of the Windows OS.
.Net 1.1 and up provides this functionality through <a href="http://msdn.microsoft.com/en-us/library/ee853281.aspx" rel="nofollow">Visual Studio for Applications</a>. An example project for this is on CodeProject named <a href="http://www.codeproject.com/KB/cs/vsascripting.aspx" rel="nofollow">VSA Scripting in .NET</a>.
With .Net 3.5 this functionality has been deprecated in favor of Powershell using the <a href="http://msdn.microsoft.com/en-us/library/system.management.automation%28VS.85%29.aspx" rel="nofollow">System.Management.Automation</a> namespace. An example project for this is on CodeProject named <a href="http://www.codeproject.com/KB/cs/HowToRunPowerShell.aspx" rel="nofollow">How to run PowerShell scripts from C#</a>.