WPF and XAML - HOWTO: Difference between revisions

From Yggenyk
Jump to navigation Jump to search
Line 1: Line 1:
[[Category:English pages]]
[[Category:English pages]]
[[Category:Software development]]
[[Category:Software development]]
==Standard Date and Time Format Strings==
* [http://msdn.microsoft.com/en-us/library/az4se3k1.aspx Standard Date and Time Format Strings]
==Troubleshooting WPF and Silverlight Designer Load Failures==
==Troubleshooting WPF and Silverlight Designer Load Failures==
http://msdn.microsoft.com/en-us/library/ff356886(VS.95).aspx
http://msdn.microsoft.com/en-us/library/ff356886(VS.95).aspx

Revision as of 04:10, 13 October 2012

Standard Date and Time Format Strings

Troubleshooting WPF and Silverlight Designer Load Failures

http://msdn.microsoft.com/en-us/library/ff356886(VS.95).aspx

Debugging a Designer Load Failure

To debug a designer load failure

  1. Open a second instance of Visual Studio.
  2. From the Debug menu, choose Attach to Process.
    The Attach To Process dialog box opens.
  3. In the Available Processes section, select the instance of devenv.exe that is loading your XAML and click Attach.
    The Visual Studio debugger attaches to the selected devenv.exe instance.
  4. From the Debug menu, choose Exceptions.
    The Exceptions dialog box opens.
  5. In the Break when exception is list, find the Common Language Runtime Exceptions name, and then check the Thrown check box.
  6. Click OK.
  7. In the first Visual Studio instance that you are debugging, reload the XAML file.
    The second instance of Visual Studio opens and displays the load exception.

Note: You can click Stop Debugging in the second instance of Visual Studio and the first instance keeps running

Label without accelerator

<source lang="csharp">

  <Label>
     <ContentPresenter RecognizesAccessKey="False" Content="_123">
     </ContentPresenter>
  </Label>

</source>

id=siteTree