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.
Reported from the forums:
"Usually the Start Debugging button in VS2013 gives a choice which resolution the Windows Phone 8 emulator image should use. After installing Xamarin for Android (Stable) this choice is gone and I could not select the destination device. After removing the Xamarin.Core component (Tools/Extensions) everything was fine again.
Seems the Xamarin.Core overwrites some Toolbar behaviours - even in WP8 projects."
"I found that if you run the emulator from the command line (xde.exe) while Visual Studio is running, that all of the installed emulator versions will show up as they are supposed to in VS. At that point you can close the version you started manually and everything will work as expected (VS will show the emulator list and launch into the one you specify)."
I have not seen this in VS2012 or VS2013, I have both addin's installed and am able to see the WP8 emulators in the drop down off the start button. But only when the WP8 project is set as startup.
Which version of the extension are they using? The forum post was posted in december which means it probably occurred in the MTVS 1.8 release which had known problems with VS2013.
Thanks for checking this out! I added a post on the forums, suggesting that those folks try version 1.10 if they haven't already.
As there is no response from 01-14-2014 so I am closing this issue. Marking As RESOLVED-NORESPONSE. Please feel free to reopen this issue if you are still getting this issue.