Skip to content

Commit 5c193d2

Browse files
authored
Merge pull request #5639 from Mikejo5000/mikejo-br16
Edits
2 parents 184e2ff + 82fed1e commit 5c193d2

10 files changed

+26
-28
lines changed

docs/debugger/debug-a-webview-control.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ ms.workload:
2121

2222
- Open the [DOM Explorer](../debugger/quickstart-debug-html-and-css.md) for a `WebView` instance, and inspect DOM elements, investigate CSS style issues, and test dynamically rendered changes to styles.
2323

24-
- Select the webpage or `iFrame` displayed in the `WebView` instance as a target in the [JavaScript Console](../debugger/javascript-console-commands.md) window, and then interact with the webpage using console commands. The console provides access to the current script execution context.
24+
- Select the webpage or `iFrame` displayed in the `WebView` instance as a target in the [JavaScript Console](../debugger/javascript-console-commands.md?view=vs-2017) window, and then interact with the webpage using console commands. The console provides access to the current script execution context.
2525

2626
### Attach the debugger (C#, Visual Basic, C++)
2727

@@ -75,7 +75,7 @@ ms.workload:
7575
> [!NOTE]
7676
> Using the console, you can interact with a single `WebView`, `iFrame`, share contract, or web worker at a time. Each element requires a separate instance of the web platform host (WWAHost.exe). You can interact with one host at a time.
7777
78-
6. View and modify variables in your app or use console commands, as described in [QuickStart: Debug JavaScript](../debugger/quickstart-debug-javascript-using-the-console.md) and [JavaScript Console commands](../debugger/javascript-console-commands.md).
78+
6. View and modify variables in your app or use console commands, as described in [QuickStart: Debug JavaScript](../debugger/quickstart-debug-javascript-using-the-console.md) and [JavaScript Console commands](../debugger/javascript-console-commands.md?view=vs-2017).
7979

8080
## See Also
8181

docs/debugger/error-unable-to-start-debugging-on-the-web-server.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,9 @@ In addition, here are some of the common error codes and a few suggestions.
8888

8989
## <a name="cannot_connect"></a> The debugger cannot connect to the remote computer
9090

91-
If you are debugging locally, this error may occur because Visual Studio is a 32-bit application, so it uses the 64-bit version of the remote debugger to debug 64-bit applications. Open your project properties and make sure that the project is configured to connect to the correct Web server and URL. (Open **Properties > Web > Servers** or **Properties > Debug** depending on your project type.)
91+
If you are debugging locally, open your project properties in Visual Studio and make sure that the project is configured to connect to the correct Web server and URL. (Open **Properties > Web > Servers** or **Properties > Debug** depending on your project type.)
92+
93+
This error may occur when debugging locally because Visual Studio is a 32-bit application, so it uses the 64-bit version of the remote debugger to debug 64-bit applications. Check your App Pool on IIS to make sure that **Enable 32-bit applications** is set to `true`, restart IIS, and try again.
9294

9395
Also, if you are using a HOSTS file, make sure it is configured correctly. For example, the HOSTS file needs to include the same project URL as in your project properties, **Properties > Web > Servers** or **Properties > Debug**, depending on your project type.
9496

docs/debugger/how-to-set-a-thread-name-in-native-code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Thread naming is possible in any edition of Visual Studio. Thread naming is usef
2222

2323
## Ways to set a thread name
2424

25-
There are two ways to set a thread name. The first is via the [SetThreadDescription](https://docs.microsoft.com/windows/desktop/api/processthreadsapi/nf-processthreadsapi-setthreaddescription) function. The second is by throwing a particular exception while the Visual Studio debugger is attached to the process. Each approach has benefits and caveats.
25+
There are two ways to set a thread name. The first is via the [SetThreadDescription](/windows/desktop/api/processthreadsapi/nf-processthreadsapi-setthreaddescription) function. The second is by throwing a particular exception while the Visual Studio debugger is attached to the process. Each approach has benefits and caveats. The use of `SetThreadDescription` is supported starting in Windows 10, version 1607 or Windows Server 2016.
2626

2727
It is worth noting that _both_ approaches can be used together, if desired, since the mechanisms by which they work are independent of each other.
2828

docs/debugger/javascript-console-commands.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "JavaScript Console commands | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "03/28/2019"
4+
ms.date: "10/17/2019"
55
ms.topic: "reference"
66
helpviewer_keywords:
77
- "JavaScript Console commands [UWP apps]"
@@ -10,18 +10,14 @@ helpviewer_keywords:
1010
author: "mikejo5000"
1111
ms.author: "mikejo"
1212
manager: jillfra
13+
monikerRange: vs-2017
1314
ms.workload:
1415
- "uwp"
1516
- "cordova"
1617
---
1718
# JavaScript Console commands in Visual Studio
1819

19-
::: moniker range=">=vs-2019"
20-
You can use commands to send messages and perform other tasks in the JavaScript Console window of Visual Studio. The information in this topic applies to Node.js apps created using Visual Studio with the **Node.js development** workload installed.
21-
::: moniker-end
22-
::: moniker range="vs-2017"
23-
You can use commands to send messages and perform other tasks in the JavaScript Console window of Visual Studio. For examples that show how to use this window, see [QuickStart: Debug JavaScript](../debugger/quickstart-debug-javascript-using-the-console.md?view=vs-2017). The information in this topic applies to Node.js app, UWP apps, and apps created using Visual Studio Tools for Apache Cordova. For info on supported console commands in Cordova apps, see [Debug Your App](https://taco.visualstudio.com/en-us/docs/debug-using-visual-studio/).
24-
::: moniker-end
20+
You can use commands to send messages and perform other tasks in the JavaScript Console window of Visual Studio. For examples that show how to use this window, see [QuickStart: Debug JavaScript](../debugger/quickstart-debug-javascript-using-the-console.md?view=vs-2017). The information in this topic applies to Node.js app, UWP apps, and apps created using Visual Studio Tools for Apache Cordova.
2521

2622
If the JavaScript Console window is closed, you can open it while you're debugging in Visual Studio by choosing **Debug** > **Windows** > **JavaScript Console**.
2723

@@ -31,6 +27,7 @@ If the JavaScript Console window is closed, you can open it while you're debuggi
3127
For info on using the console in Microsoft Edge Developer tools, see [this topic](/microsoft-edge/devtools-guide).
3228

3329
## console object commands
30+
3431
This table shows the syntax for the `console` object commands that you can use in the JavaScript Console window, or that you can use to send messages to the console from your code. This object provides a number of forms so that you can distinguish between informational messages and error messages, if you want to.
3532

3633
You can use the longer command form `window.console.[command]` if you need to avoid possible confusion with local objects named console.

docs/debugger/keyboard-shortcuts-html-and-javascript.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,22 @@
11
---
22
title: "Keyboard shortcuts (HTML and JavaScript) | Microsoft Docs"
3-
ms.date: "03/28/2019"
3+
ms.date: "10/17/2019"
44
ms.topic: "conceptual"
55
dev_langs:
66
- "CSharp"
77
- "VB"
88
- "FSharp"
99
- "C++"
10-
ms.assetid: 8d44425a-6584-477d-932e-4e10d5e79511
1110
author: "mikejo5000"
1211
ms.author: "mikejo"
1312
manager: jillfra
13+
monikerRange: vs-2017
1414
ms.workload:
1515
- "multiple"
1616
---
1717
# Keyboard shortcuts (HTML and JavaScript)
1818

19-
::: moniker range=">=vs-2019"
20-
Keyboard shortcuts in Visual Studio for debugging Node.js apps in Visual Studio with the **Node.js development** workload installed.
21-
::: moniker-end
22-
::: moniker range="vs-2017"
23-
Keyboard shortcuts in Visual Studio for debugging UWP apps using HTML and JavaScript.
24-
::: moniker-end
19+
Keyboard shortcuts in Visual Studio for debugging UWP apps using HTML and JavaScript.
2520

2621
## General shortcuts
2722

@@ -58,6 +53,6 @@ ms.workload:
5853
|Decrease selected CSS value by 1|Down Arrow|
5954

6055
## See Also
61-
- [JavaScript Console commands](../debugger/javascript-console-commands.md)
56+
- [JavaScript Console commands](../debugger/javascript-console-commands.md?view=vs-2017)
6257
- [Quickstart: Debug HTML and CSS](../debugger/quickstart-debug-html-and-css.md?view=vs-2017)
6358
- [QuickStart: Debug JavaScript](../debugger/quickstart-debug-javascript-using-the-console.md?view=vs-2017)

docs/debugger/quickstart-debug-html-and-css.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@ You can select DOM elements in three ways when debugging an app:
231231

232232
- By using the **Select Element** button (Ctrl+B).
233233

234-
- By using the `select` command, which is one of the [JavaScript Console commands](../debugger/javascript-console-commands.md).
234+
- By using the `select` command, which is one of the [JavaScript Console commands](../debugger/javascript-console-commands.md?view=vs-2017).
235235

236236
When you use the DOM Explorer window to select elements, and rest the mouse pointer on an element, the corresponding element is highlighted in the running app. You must click on the element in DOM Explorer to select it, or you can use the arrow keys to highlight and select elements.You can also select elements in DOM Explorer by using the **Select element** button. The following illustration shows the **Select Element** button.
237237

@@ -252,7 +252,7 @@ You can select DOM elements in three ways when debugging an app:
252252
- [Debug apps in Visual Studio](/visualstudio/debugger/debugging-windows-store-and-windows-universal-apps)
253253
- [Refresh an app (JavaScript)](../debugger/refresh-an-app-javascript.md)
254254
- [Debug a WebView control](../debugger/debug-a-webview-control.md)
255-
- [Keyboard shortcuts](../debugger/keyboard-shortcuts-html-and-javascript.md)
256-
- [JavaScript Console commands](../debugger/javascript-console-commands.md)
255+
- [Keyboard shortcuts](../debugger/keyboard-shortcuts-html-and-javascript.md?view=vs-2017)
256+
- [JavaScript Console commands](../debugger/javascript-console-commands.md?view=vs-2017)
257257
- [Debug HTML, CSS, and JavaScript sample code](../debugger/debug-html-css-and-javascript-sample-code.md)
258258
- [Product Support and Accessibility](https://msdn.microsoft.com/library/tzbxw1af(VS.120).aspx)

docs/debugger/quickstart-debug-javascript-using-the-console.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.workload:
1919
---
2020
# Debug JavaScript using the console in Visual Studio
2121

22-
You can use the JavaScript Console window to interact with and debug UWP apps built using JavaScript. These features are supported for UWP apps and apps created using Visual Studio Tools for Apache Cordova. For the console command reference, see [JavaScript Console commands](../debugger/javascript-console-commands.md).
22+
You can use the JavaScript Console window to interact with and debug UWP apps built using JavaScript. These features are supported for UWP apps and apps created using Visual Studio Tools for Apache Cordova. For the console command reference, see [JavaScript Console commands](../debugger/javascript-console-commands.md?view=vs-2017).
2323

2424
The JavaScript Console window allows you to:
2525

@@ -33,7 +33,7 @@ The JavaScript Console window allows you to:
3333

3434
- View JavaScript errors and exceptions, in addition to Document Object Model (DOM) and Windows Runtime exceptions.
3535

36-
- Perform other tasks, like clearing the screen. See [JavaScript Console commands](../debugger/javascript-console-commands.md) for the full list of commands.
36+
- Perform other tasks, like clearing the screen. See [JavaScript Console commands](../debugger/javascript-console-commands.md?view=vs-2017) for the full list of commands.
3737

3838
> [!TIP]
3939
> If the JavaScript Console window is closed, choose **Debug**> **Windows** > **JavaScript Console** to re-open it. The window appears only during a script debugging session.
@@ -245,9 +245,9 @@ You can also switch the execution context by using the `cd` command, but you mus
245245

246246
## See Also
247247
- [Debug apps in Visual Studio](/visualstudio/debugger/debugging-windows-store-and-windows-universal-apps)
248-
- [JavaScript Console commands](../debugger/javascript-console-commands.md)
248+
- [JavaScript Console commands](../debugger/javascript-console-commands.md?view=vs-2017)
249249
- [Refresh an app (JavaScript)](../debugger/refresh-an-app-javascript.md)
250-
- [Keyboard shortcuts](../debugger/keyboard-shortcuts-html-and-javascript.md)
250+
- [Keyboard shortcuts](../debugger/keyboard-shortcuts-html-and-javascript.md?view=vs-2017)
251251
- [Debug HTML, CSS, and JavaScript sample code](../debugger/debug-html-css-and-javascript-sample-code.md)
252252
- [Quickstart: Debug HTML and CSS](../debugger/quickstart-debug-html-and-css.md)
253253
- [Debug a WebView control](../debugger/debug-a-webview-control.md)

docs/javascript/debug-nodejs.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,9 @@ To attach the debugger from Visual Studio and hit breakpoints in client-side cod
8585

8686
![Attach to process](../javascript/media/tutorial-nodejs-react-attach-to-process.png)
8787

88+
::: moniker range="vs-2017"
8889
You know the debugger has attached correctly when the DOM Explorer and the JavaScript Console open in Visual Studio. These debugging tools are similar to Chrome Developer Tools and F12 Tools for Microsoft Edge.
90+
::: moniker-end
8991

9092
> [!NOTE]
9193
> If the debugger does not attach and you see the message "Unable to attach to the process. An operation is not legal in the current state", use the Task Manager to close all instances of Chrome before starting Chrome in debugging mode. Chrome Extensions may be running and preventing full debug mode.

docs/javascript/tutorial-nodejs-with-react-and-jsx.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -406,7 +406,9 @@ In the preceding section, you attached the debugger to server-side Node.js code.
406406

407407
![Attach to process](../javascript/media/tutorial-nodejs-react-attach-to-process.png)
408408

409+
::: moniker range="vs-2017"
409410
You know the debugger has attached correctly when the DOM Explorer and the JavaScript Console open in Visual Studio. These debugging tools are similar to Chrome Developer Tools and F12 Tools for Microsoft Edge.
411+
::: moniker-end
410412

411413
> [!NOTE]
412414
> If the debugger does not attach and you see the message "Unable to attach to the process. An operation is not legal in the current state.", use the Task Manager to close all instances of Chrome before starting Chrome in debugging mode. Chrome Extensions may be running and preventing full debug mode.

docs/xaml-tools/xaml-hot-reload-troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ If these options are selected, then go to Live Visual Tree (**Debug** > **Window
4242
XAML Hot Reload requires that the environment variable `ENABLE_XAML_DIAGNOSTICS_SOURCE_INFO` is set to 1 at the time application starts. Visual Studio sets this automatically as part of the **Debug** > **Start Debugging** (or **F5**) command. If you want to use XAML Hot Reload with the **Debug** > **Attach to Process** command instead, then set the environment variable yourself.
4343

4444
> [!NOTE]
45-
> To set an environment variable, search for "environment variable" and choose **Edit the system environment variables**. In the dialog box that opens, choose **Environment Variables**, then add it as a user variable, and set the value to `1`. To clean up, remove the variable when you are finished debugging.
45+
> To set an environment variable, use the Start button to search for "environment variable" and choose **Edit the system environment variables**. In the dialog box that opens, choose **Environment Variables**, then add it as a user variable, and set the value to `1`. To clean up, remove the variable when you are finished debugging.
4646
4747
## Verify that your MSBuild properties are correct
4848

0 commit comments

Comments
 (0)