Is there a redistributable for Windows Scripting Host?

[MikeB...@lumenvox.com]

Considering we are using VBScript as custom actions, we should provide the means
for them to run the script... unless Windows Installer is doing it natively.

thanks
Michael Bergman
Lumenvox LLC

[R. Michael Sanford]

I'm curious about this myself, but I'm pretty sure the only thing in town
you'll find that won't run VBScript out of the box is Windows 95, which most
people aren't supporting any more. Is it an option for you to just use a
launch condition to exclude anything less than windows 98? "(Version9X >
400) OR VersionNT"

<MikeB...@Lumenvox.com> wrote in message
news:ag4kn...@drn.newsguy.com...

[MikeB...@lumenvox.com]

NT 4.0 out of the box doesn't have WSH... and although we are migrating to
Win2K, we are targeting our SDK to all platforms and our design tools and engine
to NT 4.0 sp6 and above. My understanding is that IE supported VBScript
natively. Is that true of IE 5.0 and above or does the WSH get installed with
it. If WSH gets installed with IE to support VBScript and JScript then that
solves our problem since we require IE 5.0 (well no we don't for our SDK... and
that is the product I am currently working on).

Michael Bergman
Lumenvox LLC

In article <Oam6YLHJCHA.2484@tkmsftngp12>, "R. says...

[Chris Pettingill]

Check out: http://msdn.microsoft.com/scripting

There's some downloads from there that have the engines. I don't know what
sort of licensing/deployment conditions there are around distributing it.

<MikeB...@Lumenvox.com> wrote in message
news:ag4kn...@drn.newsguy.com...

[Torgeir Bakken]

MikeB...@Lumenvox.com wrote:

> NT 4.0 out of the box doesn't have WSH... and although we are migrating to
> Win2K, we are targeting our SDK to all platforms and our design tools and engine
> to NT 4.0 sp6 and above. My understanding is that IE supported VBScript
> natively. Is that true of IE 5.0 and above or does the WSH get installed with
> it. If WSH gets installed with IE to support VBScript and JScript then that
> solves our problem since we require IE 5.0 (well no we don't for our SDK... and
> that is the product I am currently working on).

Hi

IE 5.01 installs VBScript 5.1 (WSH 2.0)
IE 5.5 installs VBScript 5.5 (WSH 2.0)
IE 6 installs VBScript 5.6 (WSH 5.6)

--
torgeir

[Rich [Microsoft Windows Installer MVP]]

[Please do not mail me a copy of your followup]

MikeB...@Lumenvox.com spake the secret code
<ag4kn...@drn.newsguy.com> thusly:

>Considering we are using VBScript as custom actions, we should provide the means
>for them to run the script...

You can use AppSearch and LaunchCondition to ensure that scripting is
present before your MSI launches. I posted some database table
entries that achieved this a while back. I can repost them if you
need them. From that earlier post:

The basic idea is to detect the version of WSH based on the
version of WSHOM.OCX in [SystemFolder]. Different properties are set
to the location of the file based on the file version, so in the
LaunchConditions you can test for the appropriate version of WSH
required by your custom actions. I've attached the exported table
entries to this message.

Note that you need to adjust the sequencing of AppSearch relative to
LaunchConditions because the recommended sequence puts
LaunchConditions after AppSearch. Since AppSearch will be setting
the properties used by LaunchConditions, you need to reverse the
ordering of these two actions in your sequence tables. This should
not be a problem.
--
Ask me about my upcoming book on Direct3D from Addison-Wesley!
Direct3D Book <http://www.xmission.com/~legalize/book/>
izfree: Open source tools for Windows Installer
<http://izfree.sourceforge.net>

[MikeB...@lumenvox.com]

I would appreciate that.

thanks
Michael Bergman
Lumenvox LLC

In article <ag9v4h$vsq$1...@terabinaries.xmission.com>,
legaliz...@mail.xmission.com says...

[Will Dormann]

Torgeir Bakken wrote:
> IE 5.01 installs VBScript 5.1 (WSH 2.0)
> IE 5.5 installs VBScript 5.5 (WSH 2.0)
> IE 6 installs VBScript 5.6 (WSH 5.6)

If I do recall, it's properly to install IE *without* WSH, though.
(Un-check "VBScript Support" in Custom install). In other words,
checking to make sure that IE 5.1 or later is installed is not the same
as checking for WSH.

-WD

[Torgeir Bakken]

Will Dormann wrote:

That's right, but I think this option is removed in IE 6.0.

--
torgeir

[Phil Wilson]

Strictly speaking (and as mentioned in other posts) it's not WSH you need because if IE is
installed, so is the scripting runtime engine. WSH is one hosting mechanism for VB scripts, IE is
another, and the Windows Installer yet another, but the main functionality is in vbscript.dll, I
think.

One of the common questions about VBScript in Windows Installer is "Why doesn't
wscript.createobject() work in a custom action?", and that's because the installer isn't using WSH,
it's hosting the vbscript runtime.

<MikeB...@Lumenvox.com> wrote in message news:agc7k...@drn.newsguy.com...