Bug 30376 - "Enable developer instrumentation" has no effect in XVS because it corresponds to unused DevInstrumentationEnabled property
Summary: "Enable developer instrumentation" has no effect in XVS because it correspond...
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 3.11 (C5)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on: 30372
Blocks:
  Show dependency tree
 
Reported: 2015-05-22 20:33 UTC by Brendan Zagaeski (Xamarin Team, assistant)
Modified: 2015-10-21 15:58 UTC (History)
4 users (show)

Tags:
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 FIXED

Description Brendan Zagaeski (Xamarin Team, assistant) 2015-05-22 20:33:21 UTC
"Enable developer instrumentation" has no effect in XVS because it corresponds to unused DevInstrumentationEnabled property


This is a companion bug for Bug 30372 to provide a "practical use scenario" that can be tested in relation to that bug. Bug 30372 should be fixed first, just keeping this bug in mind. Then this bug can be verified as an extra assurance that the fix for Bug 30372 has the desired behavior in a "practical use scenario."



## Regression status: NOT a recent regression


### Bad
Xamarin   3.11.576.0 (b28d0a1)
Xamarin.Android   5.1.2.0 (2485523223ffb88567f101866d5f73da7a37ca53)


### Bad
Xamarin   3.9.547.0 (20fd2f0)
Xamarin.Android   4.20.2.1 (86274adfc6418b4c3a9d67734eb871163859b51c)


### Bad
Xamarin   3.8.150.0 (10cfd178d55287f09c85f5a1e604dfe20889a40f)
Xamarin.Android   4.20.0.28 (ba9bbbdd44cfdc4bf485e8885bd2ad24fba525f7)




(Note: if I were to attach a zipped up test case on this bug, it would be identical to the new project template, and the steps to reproduce would be identical after step 2. So I won't worry about attaching a test case.)


## Steps to reproduce

1. Create a new "Visual C# -> Android -> Blank App (Android)" project.


2. Open "Project Properties -> Android Options".


3. Un-check "Enable developer instrumentation (debugging and profiling)". (As described in Bug 30372, this sets the $(DevInstrumentationEnabled) property to False, but it should probably instead set $(DebugSymbols) to False and $(EmbedAssembliesIntoApk) to True.)


4. (Optional) Also un-check "Use Fast Deployment" to more closely match the Xamarin Studio behavior at step 3.


5. (Optional) On XVS 3.9 and earlier (where Bug 30057 is not a problem), you can also optionally disable Use Shared Runtime, and even enable the Linker if you like.


6. Save the project properties.


7. Set a breakpoint in the `OnCreate()` override, for example on `SetContentView(Resource.Layout.Main)`.


8. Start debugging the app on device or emulator (for example via "Debug -> Start Debugging").




## Results

The debugger _does_ break on the breakpoint in the `OnCreate()` override.




## Expected results

The debugger should NOT break on the breakpoint. The user has explicitly disabled the "developer instrumentation," so the user would expect breakpoints _not_ to work. Indeed if you try the same steps in Xamarin Studio on Windows, the breakpoint is _not_ hit after step 8.




## Additional version info

### Windows 8.1 (64-bit) in VMWare Fusion 6.0.6 (2684343) (with 2 CPU cores assigned to the VM)
Microsoft Visual Studio Professional 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Version 4.6.00057
Comment 1 Joaquin Jares 2015-10-21 15:58:02 UTC
Fixed via 33d9a186b78b6eb3314d59e538bbe5feb9ea624c