-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create target to output the mlaunch arguments to install+launch an app #18359
Comments
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Jun 14, 2023
…launching mobile apps. Fixes xamarin#18359. Add public targets to compute the mlaunch command lines for installing and launching mobile apps. These new targets are: * ComputeMlaunchInstallArguments * ComputeMlaunchRunArguments As part of this change, also create a few new public properties: * MlaunchPath * MlaunchRunArguments * MlaunchInstallArguments * MlaunchRunScript * MlaunchInstallScript If the *Script variables are set, the corresponding target will create a script file with the path to mlaunch + the corresponding arguments. Otherwise, it's also possible to get the arguments directly from the build log. Fixes xamarin#18359.
@Redth so we'll have two targets to execute:
Set the following properties to have these targets write the arguments to the file specified by the properties:
For whenever you can read properties from the build directly, these properties will contain the same information:
|
rolfbjarne
added a commit
that referenced
this issue
Jun 15, 2023
…launching mobile apps. Fixes #18359. (#18446) Add public targets to compute the mlaunch command lines for installing and launching mobile apps. These new targets are: * ComputeMlaunchInstallArguments * ComputeMlaunchRunArguments As part of this change, also create a few new public properties: * MlaunchPath * MlaunchRunArguments * MlaunchInstallArguments * MlaunchRunScript * MlaunchInstallScript If the *Script variables are set, the corresponding target will create a script file with the path to mlaunch + the corresponding arguments. Otherwise, it's also possible to get the arguments directly from the build log. Fixes #18359.
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Jun 15, 2023
…rguments for installing and launching mobile apps. Fixes xamarin#18359. Add public targets to compute the mlaunch command lines for installing and launching mobile apps. These new targets are: * ComputeMlaunchInstallArguments * ComputeMlaunchRunArguments As part of this change, also create a few new public properties: * MlaunchPath * MlaunchRunArguments * MlaunchInstallArguments * MlaunchRunScript * MlaunchInstallScript If the *Script variables are set, the corresponding target will create a script file with the path to mlaunch + the corresponding arguments. Otherwise, it's also possible to get the arguments directly from the build log. Fixes xamarin#18359. Backport of xamarin#18446.
rolfbjarne
added a commit
that referenced
this issue
Jun 16, 2023
…rguments for installing and launching mobile apps. Fixes #18359. (#18451) Add public targets to compute the mlaunch command lines for installing and launching mobile apps. These new targets are: * ComputeMlaunchInstallArguments * ComputeMlaunchRunArguments As part of this change, also create a few new public properties: * MlaunchPath * MlaunchRunArguments * MlaunchInstallArguments * MlaunchRunScript * MlaunchInstallScript If the *Script variables are set, the corresponding target will create a script file with the path to mlaunch + the corresponding arguments. Otherwise, it's also possible to get the arguments directly from the build log. Fixes #18359. Backport of #18446. --------- Co-authored-by: GitHub Actions Autoformatter <[email protected]>
ghost
locked as resolved and limited conversation to collaborators
Jul 15, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Create an MSBuild target to output the mlaunch arguments to install + launch an app.
The text was updated successfully, but these errors were encountered: