Bug 55688 - mlaunch support for --watchlaunchmode=complication
Summary: mlaunch support for --watchlaunchmode=complication
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: XI 10.10 (d15-2)
Hardware: PC Mac OS
: --- normal
Target Milestone: 15.3
Assignee: Rolf Bjarne Kvinge [MSFT]
Depends on:
Blocks: 55046
  Show dependency tree
Reported: 2017-04-27 15:04 UTC by Jeffrey Stedfast
Modified: 2017-07-18 11:29 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Jeffrey Stedfast 2017-04-27 15:04:31 UTC

Comment 1 Rolf Bjarne Kvinge [MSFT] 2017-05-30 13:38:37 UTC

The PR also adds a new feature: https://github.com/xamarin/xamarin-macios/pull/2144/files#diff-f35e5b594118d6353c462d941e64caabR115 which can be used to detect if mlaunch supports this.

The format is simple, use:

Comment 3 Gaurav Ganorkar 2017-07-18 09:47:49 UTC
@Rolf , 

can you please provide some steps to verify this defect ?
Comment 4 Rolf Bjarne Kvinge [MSFT] 2017-07-18 11:19:08 UTC
@Gaurav, this is an internal implementation detail for an IDE feature, and not testable (except for the IDE feature itself, which should already be tested). Thus there's no need to test this particular bug.
Comment 5 Gaurav Ganorkar 2017-07-18 11:29:28 UTC
@Rolf Thanks for your help.