Skip to content

Repo sync for protected branch #10342

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

Merged
merged 8 commits into from
Aug 13, 2024
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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/containers/deploy-app-service.md
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,10 @@ The following steps guide you through creating a basic ASP.NET Core app that wil

1. You can use an existing app service or create a new one by clicking on the **Create new Azure App Service** link. Find your existing app service in the treeview by expanding its resource group, or change the **View** setting to **Resource type** to sort by type.

![Screenshot showing choosing an App Service.](media/deploy-app-service/vs-2022/publish-app-service-linux-2.png)
![Screenshot showing choosing an App Service.](media/deploy-app-service/vs-2022/publish-app-service-linux-1.png)

> [!NOTE]
> In Visual Studio 2022 version 17.11, the default authentication method used for publishing to Azure changed from basic authentication to using an access token for authentication. To use basic authentication with Visual Studio 17.11 or later, clear the checkbox **Enable secure publishing** (not recommended).

1. If you create a new one, a resource group and app service will be generated in Azure. You can change the names if desired, as long as they are unique.

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion docs/javascript/npm-package-management.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Visual Studio integration with npm is different depending on your project type.

Starting in Visual Studio 2022, the npm package manager is available for [CLI-based projects](../javascript/javascript-in-vs-2022.md#project-templates), so you can now download npm modules similarly to the way you download NuGet packages for ASP.NET Core projects. Then you can use *package.json* to modify and delete packages.

To open the package manager, from Solution Explorer, right-click the **npm** node in your project.
To open the package manager, from Solution Explorer, right-click the **npm** node in your project and choose **Add npm package**.

:::image type="content" source="../javascript/media/vs-2022/npm-packages-open-manager-esproj.png" alt-text="Open package manager from Solution Explorer" border="true":::

Expand Down
4 changes: 2 additions & 2 deletions docs/profiling/optimize-code-using-profiling-tools.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Beginner's guide to optimizing code"
description: "Learn how to optimize code and reduce compute costs using Visual Studio profiling tools such as the CPU Usage tool, the .NET Object Allocation tool, and the Database tool."
ms.date: 07/01/2024
ms.date: 08/09/2024
ms.topic: conceptual
dev_langs:
- "CSharp"
Expand Down Expand Up @@ -31,7 +31,7 @@ Follow along and then apply these techniques to your own applications to make th

The sample application examined in this case study is a .NET application that runs queries against a database of blogs and blog posts. It utilizes the Entity Framework, a popular ORM (Object-Relational Mapping) for .NET, to interact with a SQLite local database. The application is structured to execute a large number of queries, simulating a real-world scenario where a .NET application might be required to handle extensive data retrieval tasks. The sample application is a modified version of the [Entity Framework getting started sample](/ef/core/get-started/overview/first-app).

The primary performance issue with the sample application lies in how it manages compute resources and interacts with the database. The application suffers from a common performance bottleneck that significantly impacts its efficiency and, consequently, the compute costs associated with running it. The problem includes the following symptoms:
The primary performance issue with the sample application lies in how it manages compute resources and interacts with the database. The application has a performance bottleneck that significantly impacts its efficiency and, consequently, the compute costs associated with running it. The problem includes the following symptoms:

- **High CPU Usage**: Applications may perform inefficient computations or processing tasks in a way that unnecessarily consumes a large amount of CPU resources. This can lead to slow response times and increased operational costs.

Expand Down
21 changes: 21 additions & 0 deletions docs/version-control/git-create-pull-request.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,27 @@ To create a pull request, follow these steps:

1. Once you’ve clicked **Create** on your pull request, other developers can review your changes and provide feedback.

## View pull request comments in the editor

As of Visual Studio 17.11, you can view comments and suggestions from reviewers without switching contexts to the browser.

![Screenshot showing PR comments.](./media/vs-2022/git-pull-request-comments.png)

To enable this feature, open **Tools** > **Options** > **Preview features** and make sure that **Pull Request Comments** is selected.

To view the comments for a pull request, check out any branch with an active pull request branch and select **Show comments in files** from the infobar. You can also select the PR number in the **Git Changes** window or from the Git top level menu with **Git** > **GitHub** or **Azure DevOps** > **Show comments in files**.

![Screenshot showing link to view comments in Git Changes window.](./media/vs-2022/git-pull-request-link-and-PR-number.png)

You can navigate across files and individual comments using the icons in the toolbar, or use the following keyboard shortcuts:

| Action | Keyboard shortcut |
| - | - |
| Go to the previous file in the pull request | **Ctrl**+**Shift**+**Alt**+**F6** |
| Go to the next file in the pull request | **Ctrl**+**Alt**+**F6** |
| Go to the previous comment | **Ctrl**+**Shift**+**Alt**+**F8** |
| Go to the next comment | **Ctrl**+**Alt**+**F8** |

## Next steps

To continue your journey, visit the [Fetch, pull, and sync in Visual Studio](git-fetch-pull-sync.md) page.
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.