Skip to content

Commit 1f23ac5

Browse files
committed
acrolinx edits
1 parent dc9c825 commit 1f23ac5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/debugger/how-to-test-and-debug-a-visualizer.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,9 @@ ms.subservice: debug-diagnostics
2222
> [!IMPORTANT]
2323
> Starting with Visual Studio 2022 version 17.9, visualizers can now be written in .NET 6.0+ that run out-of-process using the new VisualStudio.Extensibility model. For extensions created using the new model, see the documentation at [Create Visual Studio debugger visualizers](../extensibility/visualstudio.extensibility/debugger-visualizer/debugger-visualizers.md) instead. If you need to support older versions of Visual Studio or want to ship your custom visualizers as part of a library DLL, then use the information in this article, which applies only to the older model of extension development (VSSDK).
2424
25-
Once you have written a visualizer, you need to debug and test it.
25+
Once you write a visualizer, debug and test it.
2626

27-
One way to test a visualizer is by installing it in Visual Studio and calling it from a debugger window. (See [How to: Install a Visualizer](../debugger/how-to-install-a-visualizer.md).) If you do that, you will need to use a second instance of Visual Studio to attach and debug the visualizer, which is running in the first instance of the debugger.
27+
One way to test a visualizer is by installing it in Visual Studio and calling it from a debugger window. (See [How to: Install a Visualizer](../debugger/how-to-install-a-visualizer.md).) If you do that, then use a second instance of Visual Studio to attach and debug the visualizer, which is running in the first instance of the debugger.
2828

2929
An easier way to debug a visualizer is to run the visualizer from a test driver. The visualizer APIs make it easy to create such a driver, which is called the *visualizer development host*.
3030

@@ -45,7 +45,7 @@ An easier way to debug a visualizer is to run the visualizer from a test driver.
4545

4646
The parameters used to construct the host are the data object that will be shown in the visualizer (`objectToVisualize`) and the type of the debugger side class.
4747

48-
2. Add the following statement to call `TestShowVisualizer`. If you created your visualizer in a class library, you need to create an executable to call the class library and place this statement in your executable:
48+
2. To call `TestShowVisualizer`, add the following statement. If you created your visualizer in a class library, you need to create an executable to call the class library and place this statement in your executable:
4949

5050
```csharp
5151
DebuggerSide.TestShowVisualizer(myString);

0 commit comments

Comments
 (0)