SOLVED

Capture of package with multiple shortcuts to the same exe with different arguments

%3CLINGO-SUB%20id%3D%22lingo-sub-228185%22%20slang%3D%22en-US%22%3ECapture%20of%20package%20with%20multiple%20shortcuts%20to%20the%20same%20exe%20with%20different%20arguments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-228185%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20packaging%20tool%20fails%20in%20the%20example%20of%20the%20subject.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20aware%20that%20AppX%20shortcuts%20don't%20have%20arguments%2C%20but%20there%20are%20many%20MSI%20apps%20that%20use%20them%20and%20we%20need%20support%20for%20them%20in%20MSIX.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20appears%20that%20the%20manifest%20schema%20for%20the%20Application%20element%20does%20not%20have%20an%20arguments%20parameter%2C%20and%20that%20when%20creating%20the%20package%2C%20the%20tool%20finds%20the%20first%20shortcut%20and%20creates%20the%20Application%20element%2C%20and%20then%20for%20subsequent%20shortcuts%20skips%20them%20because%20the%20element%20is%20already%20present.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEither%20the%20schema%20needs%20extensions%2C%20or%20the%20tool%20should%20automatically%20detect%20the%20presence%20of%20arguments%20and%20remediate%20(possibly%20using%20launcher%20programs%2C%20but%20I%20hope%20not).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20issue%20is%20related%20to%20the%20previously%20reported%20issue%26nbsp%3B%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMSIX-Packaging-and-Tools%2FMSIX-Package-Support-Framework-is-now-available-on-GitHub%2Fm-p%2F228179%23M85%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMSIX-Packaging-and-Tools%2FMSIX-Package-Support-Framework-is-now-available-on-GitHub%2Fm-p%2F228179%23M85%26nbsp%3B%3C%2FA%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3Eregarding%20lack%20of%20command%20line%20arguments%2C%20but%20reported%20separately%20because%20additional%20work%20will%20be%20needed%20on%20the%20tool%20once%20the%20first%20issue%20is%20solved.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-229069%22%20slang%3D%22en-US%22%3ERe%3A%20Capture%20of%20package%20with%20multiple%20shortcuts%20to%20the%20same%20exe%20with%20different%20arguments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-229069%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20the%20work%20to%20enable%20shortcuts%20with%20parameterization%20support%20in%20our%20backlog.%20You%20can%20address%20this%20issue%20today%20with%20Package%20Support%20Framework.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EPeyman%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
MVP

The packaging tool fails in the example of the subject.

 

I am aware that AppX shortcuts don't have arguments, but there are many MSI apps that use them and we need support for them in MSIX.

 

It appears that the manifest schema for the Application element does not have an arguments parameter, and that when creating the package, the tool finds the first shortcut and creates the Application element, and then for subsequent shortcuts skips them because the element is already present.

 

Either the schema needs extensions, or the tool should automatically detect the presence of arguments and remediate (possibly using launcher programs, but I hope not).

 

This issue is related to the previously reported issue 

https://techcommunity.microsoft.com/t5/MSIX-Packaging-and-Tools/MSIX-Package-Support-Framework-is-no...

regarding lack of command line arguments, but reported separately because additional work will be needed on the tool once the first issue is solved.

1 Reply
Highlighted
Best Response confirmed by John Vintzel (Microsoft)
Solution

We have the work to enable shortcuts with parameterization support in our backlog. You can address this issue today with Package Support Framework.

 

Thanks,

Peyman