Bug 55363 - XAML compilation at assembly level causes debugger to skip assembly
Summary: XAML compilation at assembly level causes debugger to skip assembly
Status: RESOLVED ANSWERED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.4
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Stephane Delcroix
URL:
Depends on:
Blocks:
 
Reported: 2017-04-19 11:10 UTC by rtillie
Modified: 2017-04-20 14:20 UTC (History)
2 users (show)

Tags: xamlc debugger
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 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.

Related Links:
Status:
RESOLVED ANSWERED

Description rtillie 2017-04-19 11:10:36 UTC
In Visual Studio 2017 using 2.3.4.224: 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?
Comment 1 Stephane Delcroix 2017-04-20 07:05:11 UTC
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 2.3.4.231, as that version contains an an enhancement for portable pub support.
Comment 2 rtillie 2017-04-20 11:43:13 UTC
Hi Stephane,

It looks like version 2.3.4.231 solves this bug. After upgrading it seems to be working fine now.

Thanks!
Rob.