User Profile
BrettBurgeson
Brass Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: MSIX Command Line Argument
jvintzelHi John, I see from the article here: https://docs.microsoft.com/en-us/windows/msix/psf/psf-launch-apps-with-parameters we can put arguments into the config.json file inside the package to have the Launcher64.exe pass those arguments to the installed application when it is launched. What I need to do is pass a query string to the MSIX package from a link on a web page using the appinstaller and have that query string passed as an argument to the installed application when it is launched. Is there a way to do this? Thank you, Brett Burgeson10KViews0likes5CommentsRe: MSIX Command Line Argument
TIMOTHY_MANGANI'm not having any success getting arguments passed to the installed application. I added PsfLauncher64.exe and PsfRuntime64.dll to my InstallerPackageProject and I modified the config.json to execute my application being installed and left out the arguments. I also modified Package.appxmanifest to execute PsfLauncher64.exe. The appx package installs my application and launches it but does not pass any arguments to the installed application when it is launched by the installer. I have run the appx package two ways. First with a shortcut containing command line arguments. The second way is from a web page link that has a query string containing my arguments using the appinstaller. I'm really only interested in running the install from a web page using the appinstaller. I want to pass arguments as a query string. I am not interested in the install folder location. You probably need more information to understand what I may be doing wrong. Let me know what else I can tell you. Thank you for your help. Brett11KViews0likes0CommentsRe: Package.appxmanifest Executable attribute does not propagate AppxManifest.xml
TIMOTHY_MANGAN Sorry about that. I did leave a lot of detail out. Thank you for bringing that to my attention. I'm using a Windows Application Packaging Project in my Visual Studio 2019 solution to create an MSIX package for my application. I want the MSIX to use PsfLauncher64.exe so I've added that to my project and changed the Executable attribute to "PsfLauncher64.exe" in the Package/Applications/Application node of the Package.appxmanifest.xml file. When I create the app package using The Publish menu on the installer project the resulting appx file contains an AppxManifest.xml The AppManifest.xml has the executable for the installed application in the Executable attribute of the Package/Applications/Application node rather than "Psflauncher64.exe" from the Package.appxmanifest file in the installer project. I do not want to manually edit the AppManifest.xml file each time I generate a package. Is there a way to propagate the Executable setting of "PsfLauncher64.exe" automatically from the Package.appxmanifest.xml file in the installer project to the AppManifest.xml in the package when I create the app package? Thank you, Brett2.1KViews0likes1CommentRe: MSIX Command Line Argument
jvintzelI'm trying to find out how to use the package support framework to accept a query string when launched from a web site and pass that query string to the installed application as a command line argument. Is there someplace in the documentation that will help me accomplish this? Thank you, Brett11KViews0likes3CommentsRe: MSIX Command Line Argument
Hi Bogdan Mitrache Thank you for your response. We are trying to replace our click once installers with an up to date installer platform. We have customers that have multiple users that need to be able to install our application from a web server that our customers maintain. Currently the click once link supplies an argument with a path to a config file. The path to the config file is of course unique to the customer but not to each machine. We need to do the same thing with our new installer. MSIX can do that with the PSF but the package needs to be opened and the config file updated with the argument specific to the customer and repacked. We would like to avoid that step if possible so we can just have our Azure Devops pipeline produce an installer that we don't have to open up to modify the argument. One more thing is that MSIX requires the user of MSIX Core to install on versions earlier than Windows 10 build 1709. At this point I'm having trouble getting MSIX Core to build successfully. Thank you, Brett11KViews0likes6CommentsMSIX Core uses deprecated std::experimental::filesystem
We use Visual Studio 2019 and building the MSIX Core solution results in errors due to the deprecated std::experimental::filesystem. Will there be a version soon that does not use the deprecated std::experimental namespace?1.1KViews0likes2CommentsPackage.appxmanifest Executable attribute does not propagate AppxManifest.xml
I would like the Package.appxmanifest Application.Executable attribute to propagate to the AppxManifest.xml in the published package. Specifically I want the executable to be PsfLauncher64.exe and not have to change that in the manifest each time I publish. Example: <Applications> <Application Id="AppTest" Executable="PsfLauncher64.exe" The Application.Id attribute DOES propagate from Package.appxmanifest to AppxManifest.xml so I would expect the Executable attribute to do the same. Does anybody know how to make this happen? Thank you, Brett2.2KViews0likes3CommentsRe: MSIX Command Line Argument
jvintzel Is there any update on allowing parameters to be specified to the MSIX package that get passed on to the installed application? My application needs environment specific data on the command line that can be different for each installation environment without creating a whole new package for each environment. Thank you, Brett11KViews0likes20Comments
Groups
Recent Blog Articles
No content to show