SetXML

<command> [<qualifier>] [<parameter 1> ... <parameter n>] ;

select node "//applications/application[name=\"" + @FileName($3) + "\"]";

set node "C:\\Windows\\notepad.exe";

• clear;

  Empties the current document but leaves the variables and arguments untouched.

• dec <variable>;

  Decrements an integer variable. The variable must have been assigned an integer value first. See var.

• inc <variable>;

  Increments an integer variable. The variable must have been assigned an integer value first. See var.

• load <path>;

  Loads a new XML document. Any previously loaded document is discarded but the variables and arguments are untouched. This allows you to pick some data from one document and to put them in another one. The root node of the new document becomes the current node.

• var <variable> = <value>;

  Defines a variable and give it an initial value. A variable cannot be defined without being assigned a value. The variable may either be an integer or a text string. Arguments, variables and functions are valid values as well.

set node $3; // Set value of 3rd command-line parameter.

select node /* we use a user-defined argument */ $3;

The command-line arguments passed to setxml.exe may be retrieved using $0, $1, etc. and used as a command or function parameters or assigned to a variable. $0 returns the setxml.exe path, $1 returns the XML document path and $2 returns the description file. $3 and later are user-defined and may be used to pass values to the description file.

Example:

Let's say setxml.exe is called from the Command Prompt using the syntax just below.

setxml.exe pad.xml batch.txt nodeToSelect /batch

You can retrieve the user-defined argument (nodeToSelect) like this:

var nodeName = $3;
select node nodeName;

or like this:

select node $3;

Both commands above would give the same result as the command below:

select node "nodeToSelect";

Integer and text variables are supported. They are either defined using the var command, or auto-defined by one of the get commands.

Examples:

var myquery = "//channels/channel";

get node nodeValue; // nodeValue is a variable assigned by the get command

Text, integer values, arguments, functions and other variables are valid values for variables.

Variables can be used as command and function parameters. Integer variables may be used as indexes for the select child, set child or remove child commands.

Example:

var index = 1;
set child index "text of child node #1"
inc index;
set child index "text of child node #2"

The description language features a set of functions that can be used as command parameters. Functions begin with a @ character followed by the function name. Function parameters are placed between parenthesis and are separated by commas.

@<function> ( <parameter 1> [, [... <parameter n>]] )

Text, variables, arguments and functions themselves are valid function parameters.

Supported functions are listed and described below.

• @CreationTime(<path>, [<datefmt>], [<timefmt>])

  Returns the creation time of the file pointed by path.

  The second parameter is optional and describes the output format of the date. The third parameter is optional as well and describes the output format of the time. The syntax of both format parameters are identical to the formats used in the Customize Regional Optionsof the Control Panel.

  Example:

  @CreationTime("setxml.exe", "MM/dd/yyyy", )

  Output:

  04/03/2008

• @Directory(<path>)

  Returns the directory from the provided path.

  Example:

  @Directory("C:\\Windows\\notepad.exe")

  Output:

  C:\Windows

• @FileHash(<path>, <MD5|SHA1>)

  Returns the hash of the file pointed by path. SHA1 is used by default if no algorithm is not specified.

  Example:

  @FileHash("setxml.exe", )

  Output:

  36a1cb1c7b0c3b83246527f349d548d8d230dd2a

• @FileName(<path>)

  Returns the filename from the provided path.

  Example:

  @FileName("C:\\Windows\\notepad.exe")

  Output:

  notepad.exe

• @FileSize(<path>, <format>, [<precision>])

  Returns the size of the file pointed by path. Format can be "B", "KB", "MB" or "GB" to get the size as bytes, kilo-bytes, mega-bytes or giga-bytes respectively. The optional precision parameter specifies the number of decimal to print (if any). If precision is blank, the default precision is used.

  Example:

  @FileSize("setxml.exe", "B", )

  Output:

  78456

• @FullPath(<path>)

  Returns the fully qualified path from the provided path.

  Example:

  @FullPath(".\\notepad.exe")

  Output:

  C:\Windows\notepad.exe

• @LastAccessTime(<path>, [<datefmt>], [<timefmt>])

  Returns the last access time of the file pointed by path. Parameters are the same as @CreationTime.

• @LastWriteTime(<path>, [<datefmt>], [<timefmt>])

  Returns the last write time of the file pointed by path. Parameters are the same as @CreationTime.

• @LowerCase(<text>)

  Returns the text in lowercase.

  Example:

  @LowerCase("TEST")

  Output:

  test

• @UpperCase(<text>)

  Returns the text in uppercase.

  Example:

  @UpperCase("test")

  Output:

  TEST

• @Version(<path>, <format>)

  Returns the version of the executable pointed by path (if available). The second parameter controls the format of the returned string; # characters are respectively replaced by major, minor, build and qfe values of the version, any other text is copied as-is.

  Example:

  @Version("setxml.exe", "Version #.## (build #.#)")

  Output:

  Version 1.3 (build 19.4)

• @VersionInfo(<path>, <information>)

  Returns the value of the string named <information> in the version block of the executable pointed by path (if available). <information> can be Comments, CompanyName, FileDescription, etc.

  Example:

  @VersionInfo("setxml.exe", "LegalCopyright")

  Output:

  © 2008-2013, Noël Danjou. All rights reserved.

This example shows you how to create a basic PAD file in batch mode. This also shows the description language as it is generated by the Xml2Set application.

setxml.exe pad.xml createpad.txt /batch /create

This example shows you how to possibly update an existing PAD file using the file functions and arguments in batch mode. This example assumes that all the files including the executable (yourapp.exe) and the archive (yourapp.zip) of your own program are in the same folder. To run the test you can use setxml.exe and setxml.zip instead.

setxml.exe pad.xml updatepad.txt yourapp.exe yourapp.zip /batch

This example shows you how to create a new XML file and to use some file functions in batch mode.

setxml.exe fileinfo.xml fileinfo.txt readme.htm /batch /create

This example uses a larger and more advanced description file generated by Xml2Set.

setxml.exe winmeta.xml winmeta.txt /batch /create