Skip to main content

70-562 Debugging Support Windows



Locals window: It shows data in the scope. Instead of adding a watch, open the locals window, it will show the objects within the method up to the statetement executing.

Watch and quickwatch: enter a variable name, or right click them .

Call stack and Threads: to understand the context, click any methods in the stack and the corresponding file will open. When using the thread window, keep in mind that on a signle cpu, one thread is active at a time, their can be many in the list, but only one at a time is active. The active thread is the thread that is currently able to run, it's possible to select another thread and switch to it, freezing prevents execution, thawing allows execution.

The exception assistant puts in break mode and allows to check values of variables. To view possible exceptions, go to Debug->Exceptoions, and check the exception you want to break on. From the exception assistant, open the view detail link to view the properties window.

Debugging stored procedure: Debug from any project or use a database project, the advantage of a database project is it's integration to team foundation. Debugging sql server implies entering a secured environment, you will need access to debug a stored procedure(be an admin on the sql server if using Sql login), make sure to unblock firewall ports. If using windows auth to connect to sql, the user must have stored procedure permissions(sp_enablesqldebug) thats a system stored procedure on sql server.

To debug a stored procedure, open the server explore, then the sql server, and open the stored procedure. Set a breakpoint, right click the in the source file and choose step into the stored procedure, a model window shows up to provide  valid parameters values. In the same way as managed code, when debugging sql you can open the locals window, and call stack. The output window will display the results of the stored procedure.




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