Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Follow up PR for recent updates #6122

Merged
merged 2 commits into from Mar 8, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/cpp/c-cpp-properties-schema-reference.md
Expand Up @@ -9,7 +9,7 @@ MetaDescription: Schema reference for C++ project settings in Visual Studio Code
---
# c_cpp_properties.json reference

This article explains the scheme for the c_cpp_properties.json settings file.
This article explains the scheme for the `c_cpp_properties.json` settings file.

For more information about changing these settings, see [Customizing Default Settings](/docs/cpp/customize-default-settings-cpp.md) and [Configure IntelliSense for cross-compiling](/docs/cpp/configure-intellisense-crosscompilation.md).

Expand Down Expand Up @@ -92,7 +92,7 @@ For more information about changing these settings, see [Customizing Default Set
The version of the C++ language standard to use for IntelliSense.

- `configurationProvider`
The ID of a VS Code extension that can provide IntelliSense configuration information for source files. For example, use the VS Code extension ID `ms-vscode.cmake-tools` to provide configuration information from the CMake Tools extension. If you have specified a configurationProvider, the configurations that provides will take precedence over your other settings in c_cpp_properties.json.
The ID of a VS Code extension that can provide IntelliSense configuration information for source files. For example, use the VS Code extension ID `ms-vscode.cmake-tools` to provide configuration information from the CMake Tools extension. If you have specified a configurationProvider, the configurations that provides will take precedence over your other settings in `c_cpp_properties.json`.

A `configurationProvider` candidate extension must implement [vscode-cpptools-api](https://github.com/microsoft/vscode-cpptools-api).

Expand Down
4 changes: 2 additions & 2 deletions docs/cpp/config-msvc.md
Expand Up @@ -4,7 +4,7 @@ Area: cpp
TOCTitle: Microsoft C++ on Windows
ContentId: c8b779d6-79e2-49d6-acfc-430d7ac3a299
PageTitle: Configure Visual Studio Code for Microsoft C++
DateApproved: 5/13/2022
DateApproved: 3/7/2023
MetaDescription: Configure the C++ extension in Visual Studio Code to target Microsoft C++ on Windows.
---
# Configure VS Code for Microsoft C++
Expand All @@ -29,7 +29,7 @@ To successfully complete this tutorial, you must do the following:

If you have a recent version of Visual Studio, open the Visual Studio Installer from the Windows Start menu and verify that the C++ workload is checked. If it's not installed, then check the box and select the **Modify** button in the installer.

You can also install the **Desktop development with C++** workload without a full Visual Studio IDE installation. From the Visual Studio [Downloads](https://visualstudio.microsoft.com/downloads/#remote-tools-for-visual-studio-2022) page, scroll down until you see **Tools for Visual Studio 2022** under the **All Downloads** section and select the download for **Build Tools for Visual Studio 2022**.
You can also install the **Desktop development with C++** workload without a full Visual Studio IDE installation. From the Visual Studio [Downloads](https://visualstudio.microsoft.com/downloads/#remote-tools-for-visual-studio-2022) page, scroll down until you see **Tools for Visual Studio** under the **All Downloads** section and select the download for **Build Tools for Visual Studio 2022**.

![Build Tools for Visual Studio download](images/msvc/build-tools-for-vs-2022.png)

Expand Down
Binary file modified docs/cpp/images/msvc/build-tools-for-vs-2022.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/cpp/images/msvc/desktop_development_with_cpp-2022.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions docs/editor/accessibility.md
Expand Up @@ -120,7 +120,7 @@ You can use the `kbstyle(Tab)` key to jump between VS Code UI controls. Use `kbs

All elements in the workbench support tab navigation, but workbench toolbars and tab lists have only one tab stop, to avoid having too many. Once the focus is on a toolbar or a tab list, you can use the arrow keys to navigate within them.

> **Note**: Tab navigation goes in the visually natural order, with the exception of WebViews (like Markdown preview). For WebViews, we recommend using the `kb(workbench.action.focusNextPart)` and `kb(workbench.action.focusPreviousPart)` commands to navigate between the WebViews and the rest of the workbench. Alternativly you can use one of many Focus Editor commands.
> **Note**: Tab navigation goes in the visually natural order, with the exception of WebViews (like Markdown preview). For WebViews, we recommend using the `kb(workbench.action.focusNextPart)` and `kb(workbench.action.focusPreviousPart)` commands to navigate between the WebViews and the rest of the workbench. Alternatively, you can use one of many Focus Editor commands.

## Tab trapping

Expand Down Expand Up @@ -162,7 +162,7 @@ Certain features such as folding and minimap (code overview) are disabled when i

Terminal accessibility help can be accessed via `kb(workbench.action.terminal.showAccessibilityHelp)` which describes some useful tips when using a screen reader. One of the tips described is to use `kb(workbench.action.terminal.focusAccessibleBuffer)` to access the terminal's buffer, this will enter the screen reader's browse mode automatically (depending on your screen reader) and provide an accessible view of the entire terminal's buffer.

A useful accessibility setting, `terminal.integrated.tabFocusMode`, controls whether the terminal receives the tab key in favor of the workbench similar to the `editor.tabFocusMode` counterpart for the editor.
A useful accessibility setting, `terminal.integrated.tabFocusMode`, controls whether the terminal receives the `kbstyle(Tab)` key in favor of the workbench similar to the `editor.tabFocusMode` counterpart for the editor.

### Shell integration

Expand Down
2 changes: 1 addition & 1 deletion docs/editor/tasks.md
Expand Up @@ -549,7 +549,7 @@ Task properties can also be defined in the global scope. If present, they will b
}
```

>**Tip:** To get access to the global scope tasks.json file open the command palette (shift + ctrl + P) and type ```Tasks: Open User Tasks```.
>**Tip:** To get access to the global scope `tasks.json` file, open the Command Palette (`kb(workbench.action.showCommands)`) and run the **Tasks: Open User Tasks** command.

### Character escaping in PowerShell

Expand Down
5 changes: 1 addition & 4 deletions docs/java/java-spring-apps.md
Expand Up @@ -3,7 +3,7 @@ Area: java
TOCTitle: Java Spring Apps
ContentId: d34d8d3a-2093-4c67-a0a8-e02525fae8ab
PageTitle: Build and Deploy Java Spring Boot Apps to Azure Spring Cloud with Visual Studio Code
DateApproved: 6/14/2022
DateApproved: 3/2/2023
MetaDescription: Java Spring app tutorial showing how to build and deploy a Java Spring Boot microservices to Azure Spring Cloud with Visual Studio Code
---

Expand Down Expand Up @@ -111,13 +111,10 @@ If you don't have an Azure subscription, you can sign up for a [free Azure accou

<a class="install-extension-btn" href="https://azure.microsoft.com/pricing/free-trial/" target="_blank" style="background-color:#68217A">Create your free Azure account</a>


To sign in to Azure, run **Azure: Sign In** from the **Command Palette** (`kb(workbench.action.showCommands)`). Or you can sign in to your Azure Account by clicking **Sign in to Azure...** in **SPRING APPS** Explorer.


![Azure sign in code](images/java-spring-cloud/signinasa.png)


### Create an app on Azure Spring Apps

Once you are signed in to your Azure account and you have your app open in Visual Studio Code, select the Azure icon in the Activity Bar to open the Azure Explorer and you will see the Azure Spring Apps panel.
Expand Down
9 changes: 3 additions & 6 deletions docs/java/java-webapp.md
Expand Up @@ -3,7 +3,7 @@ Area: java
TOCTitle: Java Web App
ContentId: 98ddf1d3-6a8e-4b0f-a44d-e57cfdf2348c
PageTitle: Build and Deploy Java Web Apps to the cloud with Visual Studio Code
DateApproved: 11/11/2020
DateApproved: 3/2/2023
MetaDescription: Java web app tutorial showing how to build and deploy a Java web app to Azure with Visual Studio Code
---

Expand Down Expand Up @@ -99,31 +99,28 @@ To install the Azure App Service extension, open the Extensions view (`kb(workbe

To sign in to Azure, run **Azure: Sign In** from the **Command Palette** (`kb(workbench.action.showCommands)`). Or you can sign in to your Azure Account by clicking **Sign in to Azure...** in **RESOURCES** Explorer.


![Azure sign in code](images/java-webapp/login.png)

### Create a new Web App on Azure

Once the extension is installed, you can take the following steps to create a new Web App on Azure.

1. Click **Create** button on the **RESOURCES** Explorer view and select "Create App Service Web App...".
1. Click **Create** button on the **RESOURCES** Explorer view and select **Create App Service Web App...**.

2. Enter a unique name for the new Web App.

3. Select the runtime task of the Web App, for example `Java 17`.

4. Select the Java web server stack, for example `Java SE`.
5. Select a pricing tier.

5. Select a pricing tier.

![Create a Web App](images/java-webapp/create-webapp.png)

### Build and deploy to a Web App

The deploy process leverages the [Azure Account](https://marketplace.visualstudio.com/items?itemName=ms-vscode.azure-account) extension (installed along with the Azure App Service extension as a dependency) and you need to sign in with your Azure subscription. If you do not have an Azure subscription, [sign up today](https://azure.microsoft.com//free/?b=16.48) for a free 30 day account and get $200 in Azure Credits to try out any combination of Azure services.



Once you have signed in, you can open the command prompt or terminal window and build the project using Maven commands. This will generate a new `war` or `jar` artifact in the `target` directory.

```bash
Expand Down
5 changes: 3 additions & 2 deletions docs/python/editing.md
Expand Up @@ -4,7 +4,7 @@ Area: python
TOCTitle: Editing Code
ContentId: 0ccb0e35-c4b2-4001-91bf-79ff1618f601
PageTitle: Editing Python Code in Visual Studio Code
DateApproved: 11/3/2022
DateApproved: 3/6/2023
MetaDescription: Editing Python in Visual Studio Code
MetaSocialImage: images/tutorial/social.png
---
Expand Down Expand Up @@ -198,7 +198,8 @@ To customize which references need to be updated, you can toggle the checkboxes

The Python extension supports extensions such as [isort](https://marketplace.visualstudio.com/items?itemName=ms-python.isort) and [Ruff](https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff) that implement the **Sort Imports** functionality. This command consolidates specific imports from the same module into a single `import` statement, and organizes `import` statements in alphabetical order.

You can invoke this by opening the command Palette (`kb(workbench.action.showCommands)`) and running **Organize Imports**.
You can invoke this by opening the Command Palette (`kb(workbench.action.showCommands)`) and running **Organize Imports**.

> **Tip**: you can assign a keyboard shortcut to the `editor.action.organizeImports` command.

![Sorting import statements](images/editing/sortImports.gif)
Expand Down
2 changes: 1 addition & 1 deletion docs/python/jupyter-support-py.md
Expand Up @@ -120,7 +120,7 @@ The Python Interactive window also supports [Visual Studio Live Share](https://v

![Live Share for the Python Interactive window](images/jupyter/live-share-and-interactive.gif)

This feature requires the [Live Share extensions](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare) to be installed on both host and guest machines. -->
This feature requires the [Live Share extension](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare) to be installed on both host and guest machines. -->

## Variables Explorer and Data Viewer

Expand Down
4 changes: 2 additions & 2 deletions docs/python/settings-reference.md
Expand Up @@ -4,7 +4,7 @@ Area: python
TOCTitle: Settings Reference
ContentId: d256dc5c-95e9-4c02-a82f-947bf34a3517
PageTitle: Settings Reference for Python
DateApproved: 10/12/2022
DateApproved: 3/6/2023
MetaDescription: Settings Reference for the Python extension in Visual Studio Code
MetaSocialImage: images/tutorial/social.png
---
Expand Down Expand Up @@ -32,7 +32,7 @@ For general information about working with settings in VS Code, refer to [User a
| terminal.activateEnvInCurrentTerminal | `false` | Specifies whether to activate the currently open terminal when the Python extension is activated, using the virtual environment selected. |
| terminal.focusAfterLaunch | `false` | Whether to switch the cursor focus to the terminal when launching a Python terminal. |
| logging.level| `error` | Specifies the level of logging to be performed by the extension.<br> The possible levels of logging, in increasing level of information provided, are `off`, `error`, `warn`, `info`, and `debug`.<br> When set to `off`, which is not recommended, basic information will still be shown such as startup information and commands run by the Python extension.<br> At the `error` level, basic information and errors will be shown.<br> At the `warn` level, basic, error, and warning information will be shown. At the `info` level, basic, error, warning, and additional information like method execution times and return values will be shown. At this time, the `debug` level doesn't display additional information. |
| experiments.enabled | `true` | Enables [A/B experiments in the Python extension](https://aka.ms/AAjvt9q). If enabled, you may get included in proposed enhancements and/or features. |
| experiments.enabled | `true` | Enables [A/B experiments in the Python extension](https://aka.ms/AAjvt9q). If enabled, you may be provided with proposed enhancements and/or features. |

## Code analysis settings

Expand Down
2 changes: 1 addition & 1 deletion docs/remote/faq.md
Expand Up @@ -161,7 +161,7 @@ You can find the licenses for the VS Code Remote Development extensions here:

### Why aren't the Remote Development extensions or their components open source?

The Visual Studio Code Remote Development extensions and their related components use an [open planning, issue, and feature request process](https://aka.ms/vscode-remote/feedback), but are not currently open source. The extensions share source code which is also used in fully managed remote development services like [GitHub Codespaces](https://github.com/features/codespaces) and their related extensions. Given that these services also will support other proprietary products (for example Visual Studio IDE), the extensions are available under a Microsoft pre-release license like other service-based, cross-product extensions such as [Visual Studio IntelliCode](https://marketplace.visualstudio.com/items/VisualStudioExptTeam.vscodeintellicode/license) and [Visual Studio Live Share](https://marketplace.visualstudio.com/items/MS-vsliveshare.vsliveshare-pack/license) were during their preview periods.
The Visual Studio Code Remote Development extensions and their related components use an [open planning, issue, and feature request process](https://aka.ms/vscode-remote/feedback), but are not currently open source. The extensions share source code which is also used in fully managed remote development services like [GitHub Codespaces](https://github.com/features/codespaces) and their related extensions. Given that these services also will support other proprietary products (for example Visual Studio IDE), the extensions are available under a Microsoft pre-release license like other service-based, cross-product extensions such as [Visual Studio IntelliCode](https://marketplace.visualstudio.com/items/VisualStudioExptTeam.vscodeintellicode/license) and [Visual Studio Live Share](https://marketplace.visualstudio.com/items/MS-vsliveshare.vsliveshare/license) were during their preview periods.

See the [Visual Studio Code and 'Code - OSS' Differences](https://github.com/microsoft/vscode/wiki/Differences-between-the-repository-and-Visual-Studio-Code) and [Microsoft Extension Licenses](/docs/supporting/oss-extensions.md) articles for more information.

Expand Down
1 change: 0 additions & 1 deletion docs/supporting/oss-extensions.md
Expand Up @@ -62,7 +62,6 @@ As more and more teams in Microsoft contribute extensions, we realize that it ca
| [JavaScript Debugger](https://marketplace.visualstudio.com/items?itemName=ms-vscode.js-debug) | ✔ ([Repo](https://github.com/microsoft/vscode-js-debug)) | [Microsoft](https://marketplace.visualstudio.com/items/ms-vscode.js-debug/license) |
| [Kubernetes](https://marketplace.visualstudio.com/items/ms-kubernetes-tools.vscode-kubernetes-tools) | ✔ | [MIT](https://marketplace.visualstudio.com/items/ms-kubernetes-tools.vscode-kubernetes-tools/license) |
| [Live Share](https://marketplace.visualstudio.com/items/MS-vsliveshare.vsliveshare) | | [Microsoft](https://marketplace.visualstudio.com/items/MS-vsliveshare.vsliveshare/license) |
| [Live Share Audio](https://marketplace.visualstudio.com/items/MS-vsliveshare.vsliveshare-audio) | | [Microsoft](https://marketplace.visualstudio.com/items/MS-vsliveshare.vsliveshare-audio/license) |
| [Markdown Theme Kit](https://marketplace.visualstudio.com/items/ms-vscode.Theme-MarkdownKit) | ✔ | [MIT](https://marketplace.visualstudio.com/items/ms-vscode.Theme-MarkdownKit/license) |
| [Maven for Java](https://marketplace.visualstudio.com/items/vscjava.vscode-maven) | ✔ | [MIT](https://marketplace.visualstudio.com/items/vscjava.vscode-maven/license) |
| [Mezzurite](https://marketplace.visualstudio.com/items/mezzurite-devs.mezzurite) | ✔ | [MIT](https://marketplace.visualstudio.com/items/mezzurite-devs.mezzurite/license) |
Expand Down
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

This file was deleted.

8 changes: 4 additions & 4 deletions learn/collaboration/live-share.md
Expand Up @@ -27,19 +27,19 @@ For more details about what you can do with Live Share, visit the [how-to-guide]

## Get started with Live Share

To get started with using Live Share in VS Code, you'll need to download the [Live Share Extension Pack](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare) from the Extension Marketplace.
To get started with using Live Share in VS Code, you'll need to download the [Live Share](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare) extension from the VS Code Marketplace.

![Live Share Extension Pack](images/live-share/liveshare-extension-pack.png)
![Live Share extension](images/live-share/live-share-extension.png)

This extension pack includes everything you need to start collaboratively editing and debugging in real time, including integrated audio and text chat. This provides you and your team/class with a one-click installation, in order to begin pair programming, performing remote code reviews, driving interactive lectures, and more, without needing to leave Visual Studio Code.
This extension includes everything you need to start collaboratively editing and debugging in real time. This provides you and your team/class with a one-click installation, in order to begin pair programming, performing remote code reviews, driving interactive lectures, and more, without needing to leave Visual Studio Code.

Once you log into your GitHub account, you'll see the Live Share icon in the Activity Bar.

![Live Share icon in the Activity Bar](images/live-share/liveshare-icon.png)

### Starting a Live Share session

If you select **Start Collaboration session** from the Session Details menu, an invitation link to your session will automatically be copied to your clipboard. You can share this link with anyone you'd like to collaborate with, as long as they also have VS Code and the Live Share Extension Pack downloaded.
If you select **Start Collaboration session** from the Session Details menu, an invitation link to your session will automatically be copied to your clipboard. You can share this link with anyone you'd like to collaborate with, as long as they also have VS Code and the Live Share extension installed.

![Live Share invitation](images/live-share/liveshare-invitation.png)

Expand Down