Bug 13493 - Project Publish menu item missing for non-iOS projects
Summary: Project Publish menu item missing for non-iOS projects
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.3.x
Hardware: PC Windows
: High major
Target Milestone: ---
Assignee: Jose Miguel Torres
Depends on:
Reported: 2013-07-26 01:21 UTC by Pierre-Andre van Leeuwen
Modified: 2014-06-30 13:53 UTC (History)
6 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 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 Pierre-Andre van Leeuwen 2013-07-26 01:21:40 UTC
The Publish menu item on the project context menu is now replaced with "Publish iOS Application" regardless of project type. I have a web project that I can no longer publish by right-clicking on it.

I think this bug is related: https://bugzilla.xamarin.com/show_bug.cgi?id=12145.

The menu items under the normal Build menu still contains the Publish item, so it can still be done.
Comment 1 Jose Miguel Torres 2013-07-26 05:22:04 UTC
Hi Pierre,
Do you have both projects (iOS + Web) in the same solution?

Comment 2 Pierre-Andre van Leeuwen 2013-07-26 05:40:19 UTC
Yes I do.
Comment 3 Jose Miguel Torres 2013-07-26 05:54:58 UTC
Ok, I confirm the issue. I will fix it for the vNext. Apologies for the inconvenience.
Comment 4 Jose Miguel Torres 2014-05-22 04:45:07 UTC
Bug source detected and it's being fixed.