Forum Discussion
Launching Apps with Parameters
In the recent Ignite video from John Vintzel , he mentioned that launching apps with parameters is supported on OS2004. I believe I heard that this may be done in the manifest, and that you'll have to set the minimum supported to OS2004 to get the functionality.
So what is the syntax to do this in the manifest? I haven't seen any changes supporting it in the schemas.
- >As I read the documentation, this seems to only apply to uap10 hosted apps
Nope. <Application> and <Extension> attributes are 'activation info' -- Executable, EntryPoint, TrustLevel, RuntimeBehavior, Parameters, etc. That tells Windows "here's how to create a process for this activatable extension point". Parameters aren't just for host runtime.
>standard win32 based exe expose a start menu entry that uses command line arguments without the need of the PSF.
Can you elaborate?
What do you expect happen when the start menu entry is selected? A process is created with the exe? Does the process have package identity? Application identity? Is this exe referenced by an <Application> in appxmanfiest.xml? Is this just a random exe in an MSIX package not referenced by anything in appxmanifest.xml?
6 Replies
HowardKapusteinMicrosoft
<Application> and <Extension> support the uap10:Parameters=... optional parameter to pass manifested parameters to the launched process.
You can specify certain dynamic runtime values e.g.
<Application...uap10:Parameters="$(package.effectiveLocation)\bar.dat")
will launch the application with the parameter per GetPackagePathByFulName2(...PackagePathType_Effective...) + "\bar.dat"- As I read the documentation, this seems to only apply to uap10 hosted apps and not an app in general. Is the documentation (or my interpretation) incorrect?
What I am looking for is the ability to have a standard win32 based exe expose a start menu entry that uses command line arguments without the need of the PSF.- HowardKapustein>As I read the documentation, this seems to only apply to uap10 hosted apps
Nope. <Application> and <Extension> attributes are 'activation info' -- Executable, EntryPoint, TrustLevel, RuntimeBehavior, Parameters, etc. That tells Windows "here's how to create a process for this activatable extension point". Parameters aren't just for host runtime.
>standard win32 based exe expose a start menu entry that uses command line arguments without the need of the PSF.
Can you elaborate?
What do you expect happen when the start menu entry is selected? A process is created with the exe? Does the process have package identity? Application identity? Is this exe referenced by an <Application> in appxmanfiest.xml? Is this just a random exe in an MSIX package not referenced by anything in appxmanifest.xml?
