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.
Created attachment 7759 [details]
Regression in XamarinVS 3.5: breakpoints in class libraries are not hit
## Steps to reproduce
1. Download the attached test case.
2. Build and run the project (tested on "iPhone Retina (4-inch) iOS 7.1" simulator).
## Result on XamarinVS 3.5.39 + Xamarin.iOS 188.8.131.52
Visual Studio does not break on the breakpoint in the `ClassLibrary1.Class1.Class1()` constructor.
## Result on XamarinVS 3.3.47 + Xamarin.iOS 184.108.40.206
Visual Studio _does_ break on the breakpoint in the `ClassLibrary1.Class1.Class1()` constructor.
## Additional information
If you throw an exception from the `ClassLibrary1.Class1.Class1()` constructor, you can get VS to break on the call to `new ClassLibrary1.Class1();`.
If you then attempt to navigate down in the call stack into ClassLibrary1, Visual Studio displays the "Source Not Available" message:
"Frame not in module
The current stack frame was not found in a loaded module. Source cannot be shown for this location.
You can view disassembly in the Disassembly window. To always view disassembly for missing source files, change the setting in the Options dialog."
I have checked this issue with the attached sample and now with XVS 3.5.51 + X.iOS 220.127.116.11, Visual Studio break on the breakpoint in the `ClassLibrary1.Class1.Class1()` constructor as shown in screencast : http://screencast.com/t/rWIZjBPL8Xu
Hence closing this issue.