Forum Discussion

MVP

Dec 22, 2020

Solved

MakeAppX and uap3:Verb attribute parameters incorrectly validating

There appears to be some issues with how makeappx is parsing the parameters attribute. The underlying type is t:ST_Parameters which expects matching to the regex string ((?!\%[Ii].*\%[Ii]).)* ...

luiscalv
Dec 22, 2020
Hi TIMOTHY_MANGAN ,

ST_Parameters is based on ST_NonEmptyString. ST_NonEmptyString doesn't allow empty string at the beginning of the string.

AppxManifest parameter doesn't need leading space because the system injects the space between the executable and the arguments.

If you want to use quotes, you have the following options:

Parameters='/patchfile: "%1"'
Parameters="/patchfile: "%1""

Thanks
-Josue

luiscalv

Former Employee

Dec 22, 2020

Hi TIMOTHY_MANGAN ,

ST_Parameters is based on ST_NonEmptyString. ST_NonEmptyString doesn't allow empty string at the beginning of the string.

AppxManifest parameter doesn't need leading space because the system injects the space between the executable and the arguments.

If you want to use quotes, you have the following options:

Parameters='/patchfile: "%1"'
Parameters="/patchfile: "%1""

Thanks
-Josue

TIMOTHY_MANGAN

MVP

Dec 28, 2020

luiscalv By the way, the Microsoft MSIX packaging tool does produce valid MSIX packages with the syntax shown previously, but also the following syntax: <uap3:Protocol Name="powertoys" Parameters=""%1"">

So I'm not sure if we need to escape the inner quotation marks of if that is a packaging tool bug not caught in the validation.