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.
In a solution that has an Android application and a console application, selecting the console application as StartUp project and then using the global shortcut to start debugging will still try to deploy something onto the selected Android device (and start the AVD even if it is already running), making the shortcut unusable. The only way to start a debug session with the console application is to right click on the project in the solution explorer and select Debug -> Start new instance.
Forgot to add: This happens with Visual Studio 2010.
We have checked this issue with latest build:
Now, with the solution having Android and console project, after setting console project as starter project, when we run application throw global shortcut to start debugging, it does not start deploying android application and also does not start AVD.
It just runs the console project.
Hence, closing this issue.