WPF and XAML - HOWTO: Difference between revisions
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
# Open a second instance of Visual Studio. | # Open a second instance of Visual Studio. | ||
# From the Debug menu, choose Attach to Process.<br> | # From the Debug menu, choose Attach to Process.<br>The Attach To Process dialog box opens. | ||
The Attach To Process dialog box opens. | |||
#In the Available Processes section, select the instance of devenv.exe that is loading your XAML and click Attach.<br> | #In the Available Processes section, select the instance of devenv.exe that is loading your XAML and click Attach.<br> | ||
The Visual Studio debugger attaches to the selected devenv.exe instance. | The Visual Studio debugger attaches to the selected devenv.exe instance. |
Revision as of 06:33, 14 August 2010
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
- Open a second instance of Visual Studio.
- From the Debug menu, choose Attach to Process.
The Attach To Process dialog box opens. - 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.
- From the Debug menu, choose Exceptions.
The Exceptions dialog box opens.
- In the Break when exception is list, find the Common Language Runtime Exceptions name, and then check the Thrown check box.
- Click OK.
- 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>