Hello,
I had been using the vix-perl framework and hadn't had any issues, but was told that I had to switch to using the COM API under VBscript specifically. I had read an earlier post here that said that using cscript.exe is not sufficient and one must create a .wsf file and use the Windows Scripting Host in order to resolve references to the external type library ViXCOM.VixLib. The .wsf file required, taken from the powerOn.vbs example is shown below this message.
This is fine, except for the fact that WSH takes all stdout based output and puts it into modal dialog boxes because it has no stdout-like streams to attach to. This means that any debug or status information is displayed in this manner. This hampers debugging and makes the output of status or error messages during unattended build and test very difficult if not impossible.
Thus my question, and I have researched this without finding a definitive answer, is there a way to get the external type library information (mainly constants) imported into a VBscript without having to use the Windows Script Host? This would be the analog of the vix-perl product allowing one to add a script that logs information or errors to stdout as part of a build log.
Thanks in advance for your help,
Tim
<job id="powerOn">
<reference object="VixCOM.VixLib" />
<script language="VBScript" src="powerOn.vbs" />
</job>