VBScript/en - Versionsgeschichte

Cg: /* Examples */

2022-06-21T11:50:54Z

Examples

← Nächstältere Version		Version vom 21. Juni 2022, 11:50 Uhr
Zeile 106:		Zeile 106:

	==Examples==		==Examples==
	Simple examples are found in the "examples/vbScript" subfolder under the expecco installation folder.		Simple examples are found in the "testSuites/examples/vbScript" subfolder under the expecco installation folder.

	[[Category:Plugins]]		[[Category:Plugins]]

Cg: /* Executing */

2022-06-21T11:48:47Z

Executing

← Nächstältere Version		Version vom 21. Juni 2022, 11:48 Uhr
Zeile 105:		Zeile 105:
	When executed, a VBScript-block behaves like any other action block in expecco. Of course, a ScriptClient needs to be present (and in case of remote execution already running). Obviously, the ScriptClient must run on a Windows machine (or inside a virtual guest machine, running Windows).		When executed, a VBScript-block behaves like any other action block in expecco. Of course, a ScriptClient needs to be present (and in case of remote execution already running). Obviously, the ScriptClient must run on a Windows machine (or inside a virtual guest machine, running Windows).

			==Examples==
			Simple examples are found in the "examples/vbScript" subfolder under the expecco installation folder.

	[[Category:Plugins]]		[[Category:Plugins]]

Cg: /* Changes w.r.t. Previous Versions */

2022-06-21T11:47:54Z

Changes w.r.t. Previous Versions

← Nächstältere Version		Version vom 21. Juni 2022, 11:47 Uhr
Zeile 100:		Zeile 100:
	This was changed in order to support output pin writing and log-entry generation.		This was changed in order to support output pin writing and log-entry generation.

	In case your existing scripts depend on this, please change the code to use one of the above "logFail/logError" patterns.		In case your existing scripts depend on this, please change the code to use one of the above "logFail/logError" patterns (i.e. prepend ":logError:" in front of your message).

	==Executing==		==Executing==

Cg: /* Introduction */

2022-06-21T11:46:35Z

Introduction

← Nächstältere Version		Version vom 21. Juni 2022, 11:46 Uhr
Zeile 3:		Zeile 3:

	This plugin allows for Visual Basic Script (VBScript) actions to be created, edited, imported and executed in expecco.		This plugin allows for Visual Basic Script (VBScript) actions to be created, edited, imported and executed in expecco.
			VBScript actions are useful to access Windows OLE/COM objects or to create lightweight user interfaces.

			Be aware, that VBScript requires a Windows machine; this means that using this may lock you into the Windows world, and your suite may no longer execute correctly under Linux or OSX.

	For import and execution, the plugin uses the Windows executable "<code>ScriptClient.exe</code>", which is part of the expecco VBScript plugin package and technically addressed via the .NET-Bridge.		For import and execution, the plugin uses the Windows executable "<code>ScriptClient.exe</code>", which is part of the expecco VBScript plugin package and technically addressed via the .NET-Bridge.

Cg: /* Introduction */

2022-06-21T11:07:01Z

Introduction

← Nächstältere Version		Version vom 21. Juni 2022, 11:07 Uhr
Zeile 2:		Zeile 2:
	[[Bild:VBScript_Code.png\|thumb\|220px\|VBScript-Code in expecco]]		[[Bild:VBScript_Code.png\|thumb\|220px\|VBScript-Code in expecco]]

	This plugin allows for Visual Basic Script (VBScript) actions to be created, imported and executed in expecco.		This plugin allows for Visual Basic Script (VBScript) actions to be created, edited, imported and executed in expecco.
	For import and execution, the plugin uses the Windows executable "<code>ScriptClient.exe</code>", which is part of the expecco VBScript plugin package and technically addressed via the .NET-Bridge.		For import and execution, the plugin uses the Windows executable "<code>ScriptClient.exe</code>", which is part of the expecco VBScript plugin package and technically addressed via the .NET-Bridge.

Cg: /* Changes w.r.t. Previous Versions */

2022-06-20T14:12:35Z

Changes w.r.t. Previous Versions

← Nächstältere Version		Version vom 20. Juni 2022, 14:12 Uhr
Zeile 94:		Zeile 94:
	==Changes w.r.t. Previous Versions==		==Changes w.r.t. Previous Versions==
	Before 22.1, VBScript actions which generated ANY string to stderr where considered to be failing.		Before 22.1, VBScript actions which generated ANY string to stderr where considered to be failing.
	This was changed in order to support pin ~~wriging~~ and log-entry generation.		This was changed in order to support output pin writing and log-entry generation.

	In case your existing scripts depend on this, please change the code to use one of the above "logFail/logError" patterns.		In case your existing scripts depend on this, please change the code to use one of the above "logFail/logError" patterns.

Cg: /* Generating Log Entries / Reporting Failures */

2022-06-20T14:12:08Z

Generating Log Entries / Reporting Failures

← Nächstältere Version		Version vom 20. Juni 2022, 14:12 Uhr
Zeile 89:		Zeile 89:
	Wscript.StdErr.WriteLine(":logError:" & "this is an error message")		Wscript.StdErr.WriteLine(":logError:" & "this is an error message")
	Wscript.StdErr.WriteLine(":logFail:" & "this is a failure message")		Wscript.StdErr.WriteLine(":logFail:" & "this is a failure message")

	A logError or logFail will make the action be marked as unsuccessful;		A logError or logFail will make the action be marked as unsuccessful;
	however, the action continues execution (i.e. the error/fail will be reported at the end of the action's execution)		however, the action continues execution (i.e. the error/fail will be reported at the end of the action's execution)

			==Changes w.r.t. Previous Versions==
			Before 22.1, VBScript actions which generated ANY string to stderr where considered to be failing.
			This was changed in order to support pin wriging and log-entry generation.

			In case your existing scripts depend on this, please change the code to use one of the above "logFail/logError" patterns.

	==Executing==		==Executing==

Cg: /* Generating Log ENtries / Reporting Failures */

2022-06-20T14:09:39Z

Generating Log ENtries / Reporting Failures

← Nächstältere Version		Version vom 20. Juni 2022, 14:09 Uhr
Zeile 80:		Zeile 80:
	There is one difference to other script actions: because stderr is read from the VBScript interpreter only at the very end of the action, all output writes will be performed at the end of the execution. It is therefore not possible to generate values for triggering other actions while the script is executing. All writes will be effective en-bloque at the end (i.e. all outputs are always and implicitly buffered output pins)		There is one difference to other script actions: because stderr is read from the VBScript interpreter only at the very end of the action, all output writes will be performed at the end of the execution. It is therefore not possible to generate values for triggering other actions while the script is executing. All writes will be effective en-bloque at the end (i.e. all outputs are always and implicitly buffered output pins)

	==Generating Log ~~ENtries~~ / Reporting Failures==		==Generating Log Entries / Reporting Failures==

			This feature is new in the 22.1 version.

	Write one of the special patterns to the stderr:		Write one of the special patterns to the stderr:

Cg: /* Writing to Output Pins */

2022-06-20T14:09:13Z

Writing to Output Pins

← Nächstältere Version		Version vom 20. Juni 2022, 14:09 Uhr
Zeile 79:		Zeile 79:

	There is one difference to other script actions: because stderr is read from the VBScript interpreter only at the very end of the action, all output writes will be performed at the end of the execution. It is therefore not possible to generate values for triggering other actions while the script is executing. All writes will be effective en-bloque at the end (i.e. all outputs are always and implicitly buffered output pins)		There is one difference to other script actions: because stderr is read from the VBScript interpreter only at the very end of the action, all output writes will be performed at the end of the execution. It is therefore not possible to generate values for triggering other actions while the script is executing. All writes will be effective en-bloque at the end (i.e. all outputs are always and implicitly buffered output pins)

			==Generating Log ENtries / Reporting Failures==

			Write one of the special patterns to the stderr:
			Wscript.StdErr.WriteLine(":logInfo:" & "this is an info message")
			Wscript.StdErr.WriteLine(":logWarning:" & "this is a warning message")
			Wscript.StdErr.WriteLine(":logError:" & "this is an error message")
			Wscript.StdErr.WriteLine(":logFail:" & "this is a failure message")

			A logError or logFail will make the action be marked as unsuccessful;
			however, the action continues execution (i.e. the error/fail will be reported at the end of the action's execution)

	==Executing==		==Executing==

Cg: /* Connecting */

2022-06-20T13:59:50Z

Connecting

← Nächstältere Version		Version vom 20. Juni 2022, 13:59 Uhr
Zeile 21:		Zeile 21:
	Before a script can be imported or executed, expecco needs to be connected to a ScriptClient. The "''connect''"-option is found in the menu.		Before a script can be imported or executed, expecco needs to be connected to a ScriptClient. The "''connect''"-option is found in the menu.

	The ScriptClient can run either on the local or on a remote machine. Because it is a proprietary Windows program, it must run on either a Windows machine, a virtual machine running Windows or in an emulator, such as Wine. The connection is done via a .NET-bridge; therefore, expecco itself can run on any system which supports .NET (this includes Linux or OSX ~~if Mono is installed~~).		The ScriptClient can run either on the local or on a remote machine. Because it is a proprietary Windows program, it must run on either a Windows machine, a virtual machine running Windows or in an emulator, such as Wine. The connection is done via a .NET-bridge; therefore, expecco itself can run on any system which supports .NET (this includes Linux or OSX).

	In case of a local connection, the ScriptClient will be automatically started by expecco, when the first VBScript action is executed.		In case of a local connection, the ScriptClient will be automatically started by expecco, when the first VBScript action is executed.