Skip to main content

70-562 Server debugging


Server Debugging

Can debug locally or remotely

Also known as the debuggin experience...customizable from Options->Debugging

Like Configure the exception assistant, Enable Assistant.

The option is usefull in asp.net as the browser determines the possibility to debug client side code. 

The  project option also allows to debug native and SQL Server code.

The attribute needs to be on to debug, but never in production.

Debug->windows->breakpoints, gives a list of the break points, and also add colums to that window.

Tracepoints: performing actions based on breakpoints. Right click the breakpoint, select . you can use the $variables or the {Header} expression, set it to not break on the breakpoint and open the output window. This can be usefull if you don't want to step through the code or if stepping through would change the behavior of the application(thread timers).

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