Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 2292 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Step To Reproduce:
1.Launch the MonoDevelop.
2.Click on "Start a New Solution" link.
3.Choose C# > Mono for Android in left hand panel.
4.Select Mono for Android Application from the center panel.
5.Enter any name into Name field.
6.Click on "Ok" button.
7.Right Click on Solution/Project name.
8.Click on the option "Tools"
9.Click on the option "Install".
10.Provide the desired location and click on OK button.
11.Observe that it does not install at the desired location, rather it always installs under C:\Program Files (x86).
When try to install the solution to a desired location, it always installs under C:\Program Files (x86), regardless of the location provided.
It should always install at the provided location.
Mono for Android 4.0.0-12
Technically this is a usability issue, not a bug. The location is an "installation prefix" which is a very Unixy concept. IMO we should remove the packaging addin completely until we have time to redesign it, since it's mostly just confusing.
Is this something we should do now?
*** Bug 1765 has been marked as a duplicate of this bug. ***
*** Bug 1448 has been marked as a duplicate of this bug. ***
Some of the bugs I've marked as duplicates are issues with this feature. Maybe i shouldn't be marking them as dupes.