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.
In Xamarin Studio, say I am working on two projects A & B. A is my main project and B is my reference project. For both projects the Device is set to iPhone Simulator.
Now, I change the Device to iPad Simulator for Project A. If I switch to an open file or open a file of Project B, the device changes to iPhone Simulator automatically. Ok fine, understood.
But the problem happens when I switch back to my open files of Project A, the device does not change to iPad Simulator (as I had selected previously) and this creates a BIG problem cause I have to set the device to iPad again and again.
Please fix this. Let me know if you need any help.
Lluis: any idea how to fix this?
As an additional info, the scenario given above is only one example. The same thing happens in many different sceanario's as well. For eg. Set the device as iPad and add a new file and it will automatically switch to iPhone again. I sincerely hope this is fixed soon.
Thanks for your perusal.
I was giving this a thought, and I wonder why change it at all for each file? Should this not be project based? So you can store user's selection in a project file somewhere and use that. So the value will change only for different projects which is good.
This issue still exists. Any ETA on when will this be fixed?
This is not happening anymore.