Bug 1818 - 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: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-11-02 04:07 UTC by Jatin
Modified: 2011-11-04 12:46 UTC (History)
2 users (show)

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

Screenshot for the bug. (133.09 KB, image/jpeg)
2011-11-02 04:07 UTC, Jatin

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 Jatin 2011-11-02 04:07:54 UTC
Created attachment 804 [details]
Screenshot for the bug.

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.8.2
Mono for Android 1.9.2
WIndows 7
Comment 1 Lluis Sanchez 2011-11-02 09:00:16 UTC
Already fixed.
Comment 2 Jatin 2011-11-04 12:46:25 UTC
This issue is fixed now, hence closing this issue.