Skip to content

Commit 355eed2

Browse files
authored
Merge pull request #2562 from Mikejo5000/mikejo-br12
GitHub issue fixes
2 parents d1d57cc + 091d839 commit 355eed2

File tree

3 files changed

+18
-14
lines changed

3 files changed

+18
-14
lines changed

docs/debugger/create-custom-views-of-native-objects.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Create custom views of native objects"
33
description: Use the Natvis framework to customize the way that Visual Studio displays native types in the debugger
44
ms.custom: ""
5-
ms.date: "06/27/2017"
5+
ms.date: "067/20/2018"
66
ms.technology: "vs-ide-debug"
77
ms.topic: "conceptual"
88
f1_keywords:
@@ -625,7 +625,7 @@ The following intrinsic functions are supported:
625625
</Type>
626626
```
627627

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)
629629

630630
### CustomVisualizer element
631631
`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.

docs/debugger/get-started-debugging-multithreaded-apps.md

Lines changed: 14 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -106,25 +106,27 @@ To begin this tutorial, you need a multithreaded application project. Follow the
106106
#include <iostream>
107107
#include <vector>
108108

109+
using namespace;
110+
109111
int count = 0;
110112

111113
void doSomeWork() {
112114

113-
std::cout << "The doSomeWork function is running on another thread." << std::endl;
115+
cout << "The doSomeWork function is running on another thread." << endl;
114116
int data = count++;
115117
// Pause for a moment to provide a delay to make
116118
// threads more apparent.
117-
std::this_thread::sleep_for(std::chrono::seconds(3));
118-
std::cout << "The function called by the worker thread has ended." << std::endl;
119+
this_thread::sleep_for(chrono::seconds(3));
120+
cout << "The function called by the worker thread has ended." << endl;
119121
}
120122

121123
int main() {
122-
std::vector<std::thread> threads;
124+
vector<thread> threads;
123125

124126
for (int i = 0; i < 10; ++i) {
125127

126-
threads.push_back(std::thread(doSomeWork));
127-
std::cout << "The Main() thread calls this after starting the new thread" << std::endl;
128+
threads.push_back(thread(doSomeWork));
129+
cout << "The Main() thread calls this after starting the new thread" << endl;
128130
}
129131

130132
for (auto& thread : threads) {
@@ -198,17 +200,18 @@ To begin this tutorial, you need a multithreaded application project. Follow the
198200
```
199201

200202
```C++
201-
Thread::Sleep(3000);
202-
Console.WriteLine();
203+
this_thread::sleep_for(chrono::seconds(3));
204+
cout << "The function called by the worker thread has ended." << endl;
203205
```
206+
204207
```VB
205208
Thread.Sleep(3000)
206209
Console.WriteLine()
207210
```
208211

209212
#### To start debugging
210213

211-
1. Click in the left gutter of the `Thread.Sleep` or `Thread::Sleep` statement to insert a new breakpoint.
214+
1. Click in the left gutter of the `Thread.Sleep` or `this_thread::sleep_for` statement to insert a new breakpoint.
212215

213216
In the gutter on the left side of the source code editor, a red circle appears. This indicates that a breakpoint is now set at this location.
214217

@@ -226,7 +229,7 @@ To begin this tutorial, you need a multithreaded application project. Follow the
226229
```
227230

228231
```C++
229-
Thread::Sleep(3000);
232+
this_thread::sleep_for(chrono::seconds(3));
230233
```
231234

232235
```VB
@@ -255,7 +258,7 @@ In the **Parallel Stacks** window, you can switch between a Threads view and (fo
255258

256259
![Parallel Stacks Window](../debugger/media/dbg-multithreaded-parallel-stacks.png "ParallelStacksWindow")
257260

258-
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:
259262

260263
- The Main thread (left side) has stopped on `Thread.Start` (the stop point is indicated by the thread marker icon ![Thread Marker](../debugger/media/dbg-thread-marker.png "ThreadMarker")).
261264
- Two threads have entered the `ServerClass.InstanceMethod`, one of which is the current thread (yellow arrow), while the other thread has stopped in `Thread.Sleep`.

docs/msbuild/msbuild-items.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: "MSBuild Items | Microsoft Docs"
3+
description: "Use the MSBuild Include attribute of the ItemGroup to specify files to be included in a build"
34
ms.custom: ""
45
ms.date: "11/04/2016"
56
ms.technology: msbuild
@@ -14,7 +15,7 @@ ms.workload:
1415
- "multiple"
1516
---
1617
# 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.
1819

1920
Because items are named by the item type to which they belong, the terms "item" and "item value" can be used interchangeably.
2021

0 commit comments

Comments
 (0)