Skip to main content

70-562 Custom Visualizers

Framework objects are clearly viewable in the locals window during debugging. User made class librairies and their object need to provide visualizers for maintenance and debugging.

You can create your own visualizers, MS exposes the functionnality through the .Net Framework; and this is relatively easy.

Mulitple visualizers can be created per type. You can have tree views, grids; customizing it to the way that is the most usefull for debugging this particular object.

The [Serializable()] attribute has to be included to your class to allow the visual studio visualizer to parse the object.

A visualizer is a dll, a regular assembly, it requires a windows form to display the data.

The visualizer class will be implemented by the form.

The visualizer class has to inherit the DialogDebuggerVisualizer class with the DebuggerVisualizer attribute, and also the Microsoft.VisaulStudio.DebuggerVisualizers namespace.

The visualizer can be made to only read, or modify existing data.

The visualizer is a project in it's own, and would be included in a solution that include testing projects.

Among the things to do, you will have to overirde the Show method.

Testing the client visualizer can be difficult, with the TestClientVisualizer, you can test it easier.

Next deploy the visualizer in one of these two location. install directory Common7\Packages\Debugger\Visualizers or MyDocuments\Visual Studio 2008\Visualizers

Idealy, just develop it in this myDocument folder so that it doesnt need to be copied each time it's built.

You can step through the .Net Framework code if needed. Not all of the librairies are available as of now. Visual Studio needs to be configured to download the source code. Debugging->General->Enable just my code; uncheck this box, and check "Enable Source server support".


Next go to the Symbols section, Create a location, http://referencesource.microsft.com/symbols then set a location to put the symbols, you can check the box to search the above only when symbols are loaded, in order to download just what is needed, and won't need to be downloaded again unless the version changes.

Open the call stack window, show external, and right click, Load assemblies. It will download the symbols. Then just step into the code. Note that most of the time the code will show in C# even if the project is in VB.

Comments

Post a Comment

Popular posts from this blog

70-562 ListView

List View is a versatile control that allows to work with a signle control rather than many smaller controls. Provides rich sorting, deleting, editing, it is one of the most flexible grid control. Design view can fill the ListView with fake data to give an overview. In designer, the configure list view link might not show, (currently a bug), to fix configure the datasource but cancel then click configure datasource again and this time click finish and the Cofnoigure ListView link will show up in the smarttag. You can choose templates, LayoutTemplate is crucial, ItemTemplate(a row is part of a table, in a list view they are called items since they don't have to correspond to a table row), AlternatingItemTemplate, ItemSeparatorTemplate, SelectedItem, EmptyItemTemplate, EditItemTemplate, InsertItemTemplate allows to customize what the user will be presented when creating an item, EmptyDataTemplate. The itemPlaceHolder and the groupPlaceHolder are important elements as the will b...
Post a Comment
Read more

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.
4 comments
Read more

70-562 Tracing

Tracing can be enabled from the page directive, programmatically or from the web.config. This will append the trace info to the bottom of the page. There several tables of grouped trace information: Life cycle events, controls used by page, sessions state, cookies, http reuqest headers, server variables. SessionID, Time spent in each event, and check that the events are executing in the expected order. The control tree give a hierarchy of the controls in the page, and how much the control is using in the viewstate, and render by tells how much room the control uses on the page. See cookie information. And can see the Header information incase you do any kind of header manipulation. Also see query string collection. Also see the server variables passed back and forth between the server and the client application, logon user, remote user. Enable tracing when not in production, (remember to disable it when building a release... that and the debug= true setting get forg...
Post a Comment
Read more