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.
Created attachment 1572 [details]
Just like you can turn on or off "Build" for specific projects in a solution file, you can also turn on or off "Deploy" for specific projects.
The deploy step is between "Build" and "Run". WinPhone7 uses this, and in an effort to provide parity, MFA 4.1+ on VS also uses this. The common use case is you have a solution with both a WP7 and a MFA project. When you hit F5, both projects will Deploy no matter what the startup project is. Therefore, you can create configurations like "WinPhone" and "Android" where only 1 is set to Deploy.
Some places this can be seen:
- Build Menu -> Deploy Solution
- Build Menu -> Deploy <Selected Project>
- Solution Node Context Menu -> Deploy Solution
- Project Node Context Menu -> Deploy
Attached is a screenshot of how this is changed in the solution Configuration Manager in VS. MD has a similar dialog, it just does not have the Deploy checkbox.
The wrinkle is that most project types not support this, so you won't see this on a regular C# project for example.
VS project types have to implement IVsDeployableProjectCfg.QueryStartDeploy for the Deploy checkboxes and menu items to show up.
When a new project that supports Deploy is created, it is automatically set to true in the solution file:
Even if MD doesn't honor the Deploy setting, it would be nice to go ahead and get new MFA projects to add the Deploy setting to the solution file so the setting will be there if VS opens a MD created project.
*** This bug has been marked as a duplicate of bug 8183 ***