Bug 36735 - Better handling of missing "deploy" flag
Summary: Better handling of missing "deploy" flag
Status: RESOLVED INVALID
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: Normal normal
Target Milestone: 15.4
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-12-08 23:26 UTC by Mikayla Hutchinson [MSFT]
Modified: 2017-06-05 14:29 UTC (History)
5 users (show)

Tags: papercut
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED INVALID

Description Mikayla Hutchinson [MSFT] 2015-12-08 23:26:04 UTC
When the deploy flag is not set for an Android project, and you try to run it, it looks like nothing happened. 

The only hint as to what's wrong is a couple of lines in the build output:

2>------ Skipped Deploy: Project: GroceryList, Configuration: Debug Any CPU ------
2>Project not selected to build for this solution configuration 
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 1 skipped ==========

This isn't obvious, and it isn't obvious how to resolve it either.

This situation is fairly common due to XS bug 8183, so we need to handle it better.

Is there any way we could remove the need for this flag, or set it automatically? At the every least we could display a dialog telling the user how to set the flag.
Comment 2 Joaquin Jares 2017-06-05 14:29:27 UTC
This is a vey old bug and I don't think it makes sense anymore. I'm resolving as invalid, but please do reopen if you feel it still makes sense.