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 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.
I noted with disappointment that Xamarin Studio's installer has created a root level folder (/Developer) on my OS X install. Could you please look at putting these files into a more appropriate location such as /Library/Application Support/Xamarin Studio/ or something similar?
I suppose it was the Xamarin.iOS or Xamarin.Android installer, not Xamarin Studio. I'm reassigning the bug to Xamarin.iOS since the latest version still appears to put itself in /Developer, while Xamarin.Android merely creates a symlink from there to /Library/Frameworks (it might still be creating the /Developer directory though)
Xamarin.iOS installs into /Library/Frameworks/Xamarin.iOS.framework, but will still install a few files into /Developer for backwards compatibility (symlinks that point into /Library/Frameworks/Xamarin.iOS.framework). This will not change in the immediate future.
Can I delete the folder and not affect normal operation of Xamarin? I assume the backward compatibility is something internal to Xamarin?
You can try and delete it to see what happens. If something stops working, just re-install Xamarin.iOS, but I don't think you'll run into any problems.
Backward compatibility also includes scripts our customer have, samples on the web, etc.
I notice that this has been resolved as answered: I don't mean to belabour a point, but I do think it's worth you guys planning to deprecate the use of that directory as a valid install location at some point in the future.
Please just consider it — leaving files in non-standard locations isn't good form, and it sounds like this is being left in place purely for legacy reasons (which don't really exist on a platform where the vendor deprecates their IDE once a year).
If other developers are tying their scripts to `/Developer`, that's bad practice on their part and not something that should be supported.
Anyway, I'm sorry to keep raising this — I've said my bit and I'll leave this issue alone from here on out.