You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/debugger/create-custom-views-of-native-objects.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Create custom views of native objects"
3
3
description: Use the Natvis framework to customize the way that Visual Studio displays native types in the debugger
4
4
ms.custom: ""
5
-
ms.date: "06/27/2017"
5
+
ms.date: "067/20/2018"
6
6
ms.technology: "vs-ide-debug"
7
7
ms.topic: "conceptual"
8
8
f1_keywords:
@@ -625,7 +625,7 @@ The following intrinsic functions are supported:
625
625
</Type>
626
626
```
627
627
628
-
You can see an example of the UIVisualizer in the Image Watch extension used to view in-memory bitmaps: [ImageWatch](https://visualstudiogallery.msdn.microsoft.com/e682d542-7ef3-402c-b857-bbfba714f78d)
628
+
You can see an example of the UIVisualizer in the Image Watch extension used to view in-memory bitmaps: [ImageWatch](https://marketplace.visualstudio.com/items?itemName=VisualCPPTeam.ImageWatch2017)
629
629
630
630
### CustomVisualizer element
631
631
`CustomVisualizer` is an extensibility point that specifies a VSIX extension that you can write to control the visualization in code that runs in Visual Studio. For more information about writing VSIX extensions, see [Visual Studio SDK](../extensibility/visual-studio-sdk.md). Writing a custom visualizer is a lot more work than writing an XML natvis definition, but you are free from constraints about what natvis supports or doesn't support. Custom visualizers have access to the full set of debugger extensibility APIs, which can be used to query and modify the debuggee process or communicate with other parts of Visual Studio.
In this example, from left to right we get this information:
261
+
In this example, from left to right we get this information for managed code:
259
262
260
263
- The Main thread (leftside) has stopped on `Thread.Start` (thestoppointisindicatedbythethreadmarkericon ).
261
264
- Two threads have entered the `ServerClass.InstanceMethod`, one of which is the current thread (yellowarrow), while the other thread has stopped in `Thread.Sleep`.
Copy file name to clipboardExpand all lines: docs/msbuild/msbuild-items.md
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
---
2
2
title: "MSBuild Items | Microsoft Docs"
3
+
description: "Use the MSBuild Include attribute of the ItemGroup to specify files to be included in a build"
3
4
ms.custom: ""
4
5
ms.date: "11/04/2016"
5
6
ms.technology: msbuild
@@ -14,7 +15,7 @@ ms.workload:
14
15
- "multiple"
15
16
---
16
17
# MSBuild items
17
-
MSBuild items are inputs into the build system, and they typically represent files. Items are grouped into item types based on their element names. Item types are named lists of items that can be used as parameters for tasks. The tasks use the item values to perform the steps of the build process.
18
+
MSBuild items are inputs into the build system, and they typically represent files (the files are specified in the `Include` attribute). Items are grouped into item types based on their element names. Item types are named lists of items that can be used as parameters for tasks. The tasks use the item values to perform the steps of the build process.
18
19
19
20
Because items are named by the item type to which they belong, the terms "item" and "item value" can be used interchangeably.
0 commit comments