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.
In Visual Studio 2017 using 220.127.116.11: when I add XamlCompilation for the entire assembly, visual studio sees it as non-user code. When trying to debug and stepping into it, it says 'Step into: Stepping over non-user code'.
As soon as I comment out the XamlCompilation attribute, debugging works again for the assembly.
Apparently it is happening also in Xamarin Studio: https://forums.xamarin.com/discussion/89948/xaml-compilation-at-assembly-level-cause-debugger-break-point-not-fire?
That probably indicates that VS can't find the .pdb associated.
Could you check that the .pdb file is present and up-to-date (has the same timestamp as the assembly) ?
Also, you should check if it works better with 18.104.22.168, as that version contains an an enhancement for portable pub support.
It looks like version 22.214.171.124 solves this bug. After upgrading it seems to be working fine now.