http://wpfinspector.codeplex.com/wpfinspector Wiki Rss Descriptionhttp://wpfinspector.codeplex.com/wikipage?version=27<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>A quick Roadmap</h2> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Add support for storyboards, EnterActions and ExitActions </li><li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li><li>Online Update Mechanism (Notify when an update is available and automatically download the new version) </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> <p>&nbsp;</p> <p>&nbsp;</p> </div> </div><div class="ClearBoth"></div>cmoserWed, 20 Apr 2011 09:33:00 GMTUpdated Wiki: Home 20110420093300Ahttp://wpfinspector.codeplex.com/wikipage?version=26<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>A quick Roadmap</h2> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Add support for storyboards, EnterActions and ExitActions </li><li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li><li>Online Update Mechanism (Notify when an update is available and automatically download the new version) </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> <p>&nbsp;</p> <p>&nbsp;</p> </div> </div><div class="ClearBoth"></div>cmoserFri, 08 Apr 2011 09:46:16 GMTUpdated Wiki: Home 20110408094616Ahttp://wpfinspector.codeplex.com/wikipage?version=25<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>Known issues in 0.9.8</h2> <p>The following issues are known in Version 0.9.8</p> <ul> <li>The style explorer can cause an app crash in special scenarios. Get version 0.9.7 in this case. </li><li>Local default styles are not recognized. If you need this functionality, get the latest sources until the next release is here. </li><li>A memory leak can lead to &quot;Trigger too complex&quot; exceptions. If you are facing these problems, get the latest sources until the next release is here. </li></ul> <h2>A quick Roadmap</h2> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Add support for storyboards, EnterActions and ExitActions </li><li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li><li>Online Update Mechanism (Notify when an update is available and automatically download the new version) </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> <p>&nbsp;</p> <p>&nbsp;</p> </div> </div><div class="ClearBoth"></div>cmoserThu, 31 Mar 2011 06:49:18 GMTUpdated Wiki: Home 20110331064918Ahttp://wpfinspector.codeplex.com/wikipage?version=24<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>Known issues in 0.9.8</h2> <p>The following issues are known in Version 0.9.8</p> <p>&nbsp;</p> <ul> <li>The style explorer can cause an app crash in special scenarios. Get version 0.9.7 in this case. </li><li>Local default styles are not recognized. If you need this functionality, get the latest sources until the next release is here. </li></ul> <h2>A quick Roadmap</h2> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Add support for storyboards, EnterActions and ExitActions </li><li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li><li>Online Update Mechanism (Notify when an update is available and automatically download the new version) </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> <p>&nbsp;</p> <p>&nbsp;</p> </div> </div><div class="ClearBoth"></div>cmoserMon, 28 Mar 2011 05:34:14 GMTUpdated Wiki: Home 20110328053414Ahttp://wpfinspector.codeplex.com/wikipage?version=23<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>Known issues in 0.9.8</h2> <p>The following issues are known in Version 0.9.8 </p> <p></p> <ul> <li>The style explorer can cause an app crash in special scenarios. Get version 0.9.7 in this case. </li><li>Local default styles are not recognized. If you need this functionality, get the latest sources until the next release is here. </li></ul> <h2>A quick Roadmap</h2> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Enable the inspector window on Win32 level, to make it operable also when a modal dialog is open </li><li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li><li>Online Update Mechanism (Notify when an update is available and automatically download the new version) </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> <p></p> <p></p> </div> </div><div class="ClearBoth"></div>cmoserMon, 28 Mar 2011 05:31:58 GMTUpdated Wiki: Home 20110328053158Ahttp://wpfinspector.codeplex.com/wikipage?version=22<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>A quick Roadmap</h2> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Enable the inspector window on Win32 level, to make it operable also when a modal dialog is open </li><li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li><li>Online Update Mechanism (Notify when an update is available and automatically download the new version) </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> </div> </div><div class="ClearBoth"></div>cmoserSat, 19 Mar 2011 01:13:01 GMTUpdated Wiki: Home 20110319011301Ahttp://wpfinspector.codeplex.com/wikipage?version=21<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>A quick Roadmap</h2> <p>For <strong>Version 0.9.8</strong> I plan to do the following:</p> <ul> <li>Implement a new cool version of the &quot;Style Explorer&quot; </li><li>Store application settings (window position, rule settings, etc.) </li><li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Add more details to the trigger view </li></ul> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Enable the inspector window on Win32 level, to make it operable also when a modal dialog is open </li><li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li><li>Online Update Mechanism (Notify when an update is available and automatically download the new version) </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> </div> </div><div class="ClearBoth"></div>cmoserWed, 16 Mar 2011 20:25:42 GMTUpdated Wiki: Home 20110316082542Phttp://wpfinspector.codeplex.com/wikipage?version=20<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>A quick Roadmap</h2> <p>For <strong>Version 0.9.8</strong> I plan to do the following:</p> <ul> <li>Implement a new cool version of the &quot;Style Explorer&quot; </li><li>Store application settings (window position, rule settings, etc.) </li><li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Add more details to the trigger view </li></ul> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Enable the window on Win32 level, to make it operable also when a modal dialog is open </li><li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li><li>Online Update Mechanism (Notify when an update is available and automatically download the new version) </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> </div> </div><div class="ClearBoth"></div>cmoserWed, 16 Mar 2011 20:25:11 GMTUpdated Wiki: Home 20110316082511Phttp://wpfinspector.codeplex.com/wikipage?version=19<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>A quick Roadmap</h2> <p>For <strong>Version 0.9.8</strong> I plan to do the following:</p> <ul> <li>Implement a new cool version of the &quot;Style Explorer&quot; </li><li>Store application settings (window position, rule settings, etc.) </li><li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Add more details to the trigger view </li></ul> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li><li>Online Update Mechanism (Notify when an update is available and automatically download the new version) </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> </div> </div><div class="ClearBoth"></div>cmoserWed, 16 Mar 2011 12:46:30 GMTUpdated Wiki: Home 20110316124630Phttp://wpfinspector.codeplex.com/wikipage?version=18<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>A quick Roadmap</h2> <p>For <strong>Version 0.9.8</strong> I plan to do the following:</p> <ul> <li>Implement a new cool version of the &quot;Style Explorer&quot; </li><li>Store application settings (window position, rule settings, etc.) </li><li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Add more details to the trigger view </li></ul> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> </div> </div><div class="ClearBoth"></div>cmoserTue, 15 Mar 2011 06:30:20 GMTUpdated Wiki: Home 20110315063020Ahttp://wpfinspector.codeplex.com/wikipage?version=17<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>Roadmap</h2> <p>For <strong>Version 0.9.8</strong> I plan to do the following:</p> <ul> <li>Implement a new cool version of the &quot;Style Explorer&quot; </li><li>Store application settings (window position, rule settings, etc.) </li><li>Add a collapsible panel to the rules view (including disabling of rules) </li><li>Add more details to the trigger view </li></ul> <p>Before <strong>Version, 1.0</strong> I plan to do the following:</p> <ul> <li>Finish the implementation of the binding editor </li><li>Improve synchronization between logical and visual tree </li><li>Add better visualizers for resource entries (e.g. styles </li><li>Add more editors for special data types in the property grid </li></ul> <p>Ideas for <strong>future versions</strong>:</p> <ul> <li>Add support for silverlight (the SilverlightInspector :-) </li><li>Refactor the whole app to have a client view and a remote agent </li><li>Add plugin support (provide a data model and a public API) </li><li>Add a UIAutomation view (like in Spy&#43;&#43;) </li><li>Allow some manipulations in the tree (remove items, reorder, evt. add) </li><li>And a lot more... </li></ul> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> </div> </div><div class="ClearBoth"></div>cmoserTue, 15 Mar 2011 06:29:51 GMTUpdated Wiki: Home 20110315062951Ahttp://wpfinspector.codeplex.com/wikipage?version=16<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="http://www.twitter.com/moser_christian" target="_blank">@moser_christian</a><br> Web: <a href="http://www.wpftutorial.net" target="_blank">www.wpftutorial.net</a></p> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> </div> </div><div class="ClearBoth"></div>cmoserFri, 11 Mar 2011 14:56:11 GMTUpdated Wiki: Home 20110311025611Phttp://wpfinspector.codeplex.com/wikipage?version=15<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <p><strong>Contact Information:</strong><br> Christian Moser<br> E-Mail: <a href="mailto:moc@zuehlke.com">moc@zuehlke.com</a><br> Twitter: <a href="www.twitter.com/moser_christian">@moser_christian</a><br> Web: <a href="www.wpftutorial.net">www.wpftutorial.net</a></p> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> </div> </div><div class="ClearBoth"></div>cmoserFri, 11 Mar 2011 14:55:17 GMTUpdated Wiki: Home 20110311025517Phttp://wpfinspector.codeplex.com/wikipage?version=14<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> <h2>Auto-Checks for Performance, Maintainability and Stability</h2> <p>Finally WPF Inspector includes a set of rules for performance, maintainability and stability of a WPF application. These rules are continously monitored while the inspector is running. Violations are shown as informations, warnings or errors on the bottom of the window.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector8.png" alt="Rule checking"></p> </div> </div><div class="ClearBoth"></div>cmoserFri, 11 Mar 2011 01:07:35 GMTUpdated Wiki: Home 20110311010735Ahttp://wpfinspector.codeplex.com/wikipage?version=13<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> <h2>Resource explorer</h2> <p>Another useful feature of the WPF Inspector is the resource explorer. It lists up all resources that are visible for the currently selected element. They can be either local, inherited or theme resources.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector7.png" alt="Style tracing"></p> </div> </div><div class="ClearBoth"></div>cmoserFri, 11 Mar 2011 01:01:34 GMTUpdated Wiki: Home 20110311010134Ahttp://wpfinspector.codeplex.com/wikipage?version=12<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> <h2>Style tracing</h2> <p>Styles are often inherited multiple times. So it's hard to know which setter finally affects the value. The style tracer of WPF Inspector easily shows the inheritance of styles and the overwritten values.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector6.png" alt="Style tracing"></p> </div> </div><div class="ClearBoth"></div>cmoserFri, 11 Mar 2011 00:58:13 GMTUpdated Wiki: Home 20110311125813Ahttp://wpfinspector.codeplex.com/wikipage?version=11<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debugging Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> </div> </div><div class="ClearBoth"></div>cmoserFri, 11 Mar 2011 00:52:03 GMTUpdated Wiki: Home 20110311125203Ahttp://wpfinspector.codeplex.com/wikipage?version=10<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> <h2>Debug Triggers</h2> <p>Triggers are very powerful, but they can also be very tricky to debug, since they are part of WPF, so there is no chance to set a breakpoint and see the values. WPF Inspector provides the very unique functionality to live see the values and conditions of triggers.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector5.png" alt="The property grid"></p> </div> </div><div class="ClearBoth"></div>cmoserFri, 11 Mar 2011 00:51:46 GMTUpdated Wiki: Home 20110311125146Ahttp://wpfinspector.codeplex.com/wikipage?version=9<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types including a search. The square behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> <h2>See the DataContext</h2> <p>Another useful functionality is to see the content of the DataContext. This is very helpful to search for problems in bindings. The property grid updates live and allows expansion of complex types.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector4.png" alt="The property grid"></p> </div> </div><div class="ClearBoth"></div>cmoserFri, 11 Mar 2011 00:47:39 GMTUpdated Wiki: Home 20110311124739Ahttp://wpfinspector.codeplex.com/wikipage?version=8<div class="wikidoc"> <div> <h1>WPF Inspector</h1> <h2>Introduction</h2> <p>WPF Inspector is a utility that attaches to a running WPF application to troubleshoot common problems with layouting, databinding or styling. WPF Inspector allows you to explore a live view of the logical- and visual tree, read and edit property values&nbsp;of elements, watch the data context, debug triggers, trace styles and much more.</p> <h2>Attaching to a running application</h2> <p>When WPF Inspector is launched, you see a list of running WPF applications. Doubleclick one or select and press &quot;Attach&quot; to start the inspection.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector1.png" alt="Attaching to a running application" width="415"></p> <h2>Inspecting the visual and logical tree</h2> <p>After attaching to the application, the inspector window is opened. It shows the elements of either the visual or logical tree. By selecting one, you can see and edit all properties of the elements.</p> <p>Hovering over the application while pressing the CTRL key automatically selects the element that is below the cursor. By pressing CTRL&#43;SHIFT you can also select parts of the control template.</p> <p>Major parts of the view are marked bold. The number next to the element shows the number of descendants. When hovering over an element in the tree, a tooltip shows the visual representation of the element.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector2.png" alt="Inspecting logical and visual tree"></p> <h2>View and edit Properties</h2> <p>WPF Inspector provides a mature property grid that includes editors for all common data types. The box behind the property shows the source of the value. If the value is databound, a yellow border is shown and you can see the binding expression. Modified values are highlighted by a blue background for a few seconds. You can also set breakpoints to any property that breaks into the debugger, when the value changes.</p> <p><img src="http://www.wpftutorial.net/images/wpfinspector3.png" alt="The property grid"></p> </div> </div><div class="ClearBoth"></div>cmoserFri, 11 Mar 2011 00:42:33 GMTUpdated Wiki: Home 20110311124233A