6 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• vs commented  ·  January 28, 2013 11:38 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  +3

• Roman Romaniv commented  ·  January 26, 2013 5:36 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  + 3

  Something like SL5 xaml debugging.

• Jamie Clayton commented  ·  April 2, 2012 5:32 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  It would also be ok if the XAML design errors could be displayed prior to running the application. E.g. StaticResource references that don't exist, Source paths that are relative, making it a pain to move files around. All these currently cost time to re-test and find rather than let the IDE warn you of the issue prior to build and debug.

• swythan commented  ·  November 3, 2011 4:11 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  +3 for breakpoints in XAML for WPF

• Nicolas Séveno commented  ·  October 7, 2011 2:43 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please, make the breakpoints in XAML available for WPF projects too ! Not only for silverlight 5...

• Yaniv Feinberg commented  ·  October 4, 2011 10:26 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Thank you for your suggestion. We agree that debugging XAML can be difficult and we are pleased to let you know that one of the tooling enhancements we have added is the ability to debug binding and set breakpoints in XAML for Silverlight 5.”.

  YanivF (MSFT)