Bug 19789 - Suggested alternative to disabling the Publish Android Application menu item when Use Shared Mono Runtime is selected.
Summary: Suggested alternative to disabling the Publish Android Application menu item ...
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 1.12.x
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-05-14 20:21 UTC by Jon Goldberger [MSFT]
Modified: 2016-12-27 23:01 UTC (History)
6 users (show)

Tags:
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 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:
Status:
RESOLVED NOT_REPRODUCIBLE

Comment 1 Jon Goldberger [MSFT] 2014-05-14 20:23:09 UTC
From case:
May I make a few suggestions?

The “Publish iOS Application…” option should probably be grayed out for android applications

The “Publish Android Application..” would be easier to use if it were enabled but gave you an error message telling you to disable the shared runtime.
Comment 4 Jose Gallardo 2016-12-27 23:01:45 UTC
This issue cannot longer be reproduced with the new Archive Manager included in Xamarin for VS.
Marking the bug accordingly.

Thanks for reporting.