Bug 1977 - While creating a new solution under C#, the option Mono for Android is missing
Summary: While creating a new solution under C#, the option Mono for Android is missing
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 1.9.3
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-11-10 02:49 UTC by Saurabh
Modified: 2011-11-16 03:16 UTC (History)
2 users (show)

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

MonoforAndroid (44.13 KB, image/jpeg)
2011-11-10 02:52 UTC, Saurabh

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 Saurabh 2011-11-10 02:49:28 UTC
Steps to reproduce:

1.Launch the MonoDevelop.
2.Click on "Start a New Solution" link.
3.Click on triangle icon on C#.
4.Observe that the option Mono for Android is missing. 

Actual result:

Under C#, the option Mono for Android is missing. However, Mono for Android is
already installed. Refer to the attached screenshot.

Expected result:

Under C#, following options should appear:

Mono For Android


MonoDevelop 2.9.0
Mono for Android 1.9.3
Mac 10.6
Comment 1 Saurabh 2011-11-10 02:52:53 UTC
Created attachment 861 [details]
Comment 2 Alex Corrado [MSFT] 2011-11-10 12:53:19 UTC
This was due to the wrong compatible addins version being set in the release parameters. A new package was created that fixed this.
Comment 3 Saurabh 2011-11-16 02:33:22 UTC
This is working fine now hence closing