Sorry for the duplicate posting, the website indicated an error after the first one. Please read the most recent one. Thank you.
Hello all,
I'm hoping that someone can help me. I started off using vix-perl to do unattended installs and testing, and was doing just fine, but I've had to change to using the VBScript/COM variant instead, so I am grappling with development environment issues related to VBScript.
I read a related post that said that you can't just use cscript.exe, you have to use the Windows Scripting Host in order to reference the type library "VixCOM.VixLib" so that the constants necessary to make these calls are accessible. A sample of the required .wsf file from the powerOn.vbs example is shown below.
Because WSH is required, any sort of stdout type output which would be very useful for debugging is put into a modal dialog box and stops script execution. This not only hampers debugging, but isn't usable in an unattended build/test environment.
Does someone know a way around having to use WSH to make the Constants in the type library accessible?
Many thanks for your help,
Tim Meese
<job id="powerOn">
<reference object="VixCOM.VixLib" />
<script language="VBScript" src="powerOn.vbs" />
</job>