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 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.
The current license folder is C:\ProgramData\MonoTouch\License
We should try to be moving away from 'MonoTouch' wherever possible, so something like ...\Xamarin.iOS or ...\Xamarin\iOS
I would prefer Xamarin\iOS and Xamarin\Android if possible.
Any other suggestions?
PJ Looks like this method
static LicenseToolInfo GetMonoTouchInfo ()
static LicenseToolInfo GetMonoDroidInfo ()
in Activation\ActivationService.cs are the methods that would need to change to refer to different directories.
This may have wider ramifications so I think the compiler and Activation teams need to reach an agreement on how best to change these and if that should be done before the big release.
Sounds good to push to V2 at the earliest.
This isn't going to happen for 1.4, moving to 1.6.x milestone.
I don't think this is something we really want to do. It requires changing a lot of code and the benefit is negligible.
If you want to do this change it will have to be co-ordinated across all teams - Xamarin Studio, Android, MonoTouch and also XamarinVS. It will affect forwards and backwards compatibility across the products too which will have to be taken into account.
Given that this bug has no discussion activity since 2013 and that as Alan commented is a multi team effort without visible benefits, I mark this issue as Resolved > Not On Roadmap.
Feel free to re open it if someone still considers that worth it.