Difference: InvokingWindowsShellFunctions (3 vs. 4)

Revision 42020-05-12 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="RunningWindowsFunctionsFromAPPX"

Invoking Windows Shell Functions

In order to invoke a Windows shell function (such as a batch file or executable) from APPX for Windows, you can use a syntax similar to the following. (You'll have to break the SET statement apart into multiple APPENDs, but it is presented here as single strings, for clarity.)

Line: 13 to 13

This assumes the command we want to run is already formatted in --- TEMP 512. We enclose the entire command in quotes in case of embedded spaces. The '/w' switch tells APPX to wait for the command to complete before continuing. If you don't need to wait, you can leave that switch out.

Changed:

<
<

You can also use the full path & file name of a file directly in the RUN command, ie, RUN C:\WINDOWS\SYSTEM32\NOTEPAD.EXE, however note that APPX will not wait for the command to complete. If you need to wait for the command to complete, use the '/w cmd.exe /c' syntax. Remember that when you use the RUN command, it will be executed on the server, not the client. If you need to run the command on the client PC, see .CLIENT LOAD URL.

>
>

To pass parameters to the command, simply execute PASS <field name> or PASS <Filename>, then append a $* to your command. For example:

      SET      --- TEMP 80                    =      APARAMETER

View topic | History: r4 < r3 < r2 < r1 | More topic actions...