Skip to main content

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 forgotten often). All this Tracing nfomation is very insightfull when learning asp.net.

It is possible to use the TraceContext class for adding information like Trace.Write and Trace.Warn, this last one displayed in red. Each of these has overloads with single message, category and message, and exception.

The trace object is available from the page object.

TraceContext.IsEnabled can be used to check if trace is enabled before writing. Also, this is a set property, Tracing can be enabled programmaticaly using IsEnabled, and the TraceMode can be set to change how the information is grouped.

Having trace enabled to tru in the web.config shows trace.axd localy only, while false will show to all remote users.

When writeToDiagnosticsTrace is enabled, it also writes to tracelisteners on the system.



Comments

Post a Comment

Popular posts from this blog

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

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.
Post a Comment
Read more

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. T...
Post a Comment
Read more