You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On stackoverflow thread there is an information, that you can override variables in wix bundle via command line parameters. But as I can see, this is done for WixStd Bootstrapper Application, in method ProcessCommandLine, and there is no possibility to override variables for Managed Bootstrapper Application. I know that I can parse arguments manually in my MBA in OnStartup method. This would be nice to have this functionality for all types of applications, so it seems to me that the logic for parsing command line arguments and initialization of the wix variables should be placed somewhere in the burn core, or engine, or whatever else, where it will be available
Originally opened by stukselbax
The text was updated successfully, but these errors were encountered:
It's in the 4.x milestone. The 4 means it will not be accepted in the wix3 repo, the .x means no one has signed up for it so it's not scheduled for a release.
On stackoverflow thread there is an information, that you can override variables in wix bundle via command line parameters. But as I can see, this is done for WixStd Bootstrapper Application, in method ProcessCommandLine, and there is no possibility to override variables for Managed Bootstrapper Application. I know that I can parse arguments manually in my MBA in OnStartup method. This would be nice to have this functionality for all types of applications, so it seems to me that the logic for parsing command line arguments and initialization of the wix variables should be placed somewhere in the burn core, or engine, or whatever else, where it will be available
The text was updated successfully, but these errors were encountered: