How to use --process-start-args when running setup.exe?

[davetimmins]

Hi,

I'm wanting to pass some cmd args to my app when initially installing the application so if I run the setup.exe can I do this? I found the process-start-args flag but I can't get it to pass anything through to my application.

I've tried getting the args in my app but it only shows --install.

[davetimmins]

Looks like this will be addressed with #296 hopefully?

[GianLorenzetto]

Hi,

I was wondering if there is any movement on this issue (or #296)?

This feature would be really useful for automated "run or install" scenarios.

[anaisbetts]

--process-start-args doesn't do anything related to handling initial arguments passed to Setup.exe, getting arguments from Setup.exe would not be very easy to do. What do people want to do with this?

[GianLorenzetto]

Hi Paul,

We have a launcher app that will either fire up the app or run the setup.exe if not already installed. The launcher passes some configuration to the app, so it would be nice to pass the same arguments to setup.exe, which in turn passes them along to the app (when auto-run, post-install).

Our work-around for the moment is to just run the setup.exe with the /s switch and then launch the installed app as usual.

I imagine it's not a very common use case, but I see a number of people have requested something similar and I was just curious if it was on the radar.

I manually made the modifications from #296 and it seemed to be working by calling Squirrel.exe with the --install and --prcess-start-args switches (I couldn't fully test as the Setup app wasn't building for some reason I haven't looked into yet).

Cheers

[davetimmins]

I wanted to be able to pass some initial args to set config values when the application is installed, this is so it can be configured per environment rather than having to create a specific build per client.

[simader]

Is there any update on this? I have the same issue.
Why was the pull-request not approved?