Skip to content

Commit de9e515

Browse files
Learn Build Service GitHub AppLearn Build Service GitHub App
authored andcommitted
Merging changes synced from https://github.com/MicrosoftDocs/visualstudio-docs-pr (branch live)
2 parents 4b1c04a + d34728f commit de9e515

File tree

9 files changed

+28
-4
lines changed

9 files changed

+28
-4
lines changed

docs/containers/deploy-app-service.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,10 @@ The following steps guide you through creating a basic ASP.NET Core app that wil
9999

100100
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.
101101

102-
![Screenshot showing choosing an App Service.](media/deploy-app-service/vs-2022/publish-app-service-linux-2.png)
102+
![Screenshot showing choosing an App Service.](media/deploy-app-service/vs-2022/publish-app-service-linux-1.png)
103+
104+
> [!NOTE]
105+
> 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).
103106
104107
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.
105108

Loading
Loading

docs/javascript/npm-package-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Visual Studio integration with npm is different depending on your project type.
3636

3737
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.
3838

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

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

docs/profiling/optimize-code-using-profiling-tools.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Beginner's guide to optimizing code"
33
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."
4-
ms.date: 07/01/2024
4+
ms.date: 08/09/2024
55
ms.topic: conceptual
66
dev_langs:
77
- "CSharp"
@@ -31,7 +31,7 @@ Follow along and then apply these techniques to your own applications to make th
3131

3232
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).
3333

34-
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:
34+
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:
3535

3636
- **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.
3737

docs/version-control/git-create-pull-request.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,27 @@ To create a pull request, follow these steps:
5757

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

60+
## View pull request comments in the editor
61+
62+
As of Visual Studio 17.11, you can view comments and suggestions from reviewers without switching contexts to the browser.
63+
64+
![Screenshot showing PR comments.](./media/vs-2022/git-pull-request-comments.png)
65+
66+
To enable this feature, open **Tools** > **Options** > **Preview features** and make sure that **Pull Request Comments** is selected.
67+
68+
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**.
69+
70+
![Screenshot showing link to view comments in Git Changes window.](./media/vs-2022/git-pull-request-link-and-PR-number.png)
71+
72+
You can navigate across files and individual comments using the icons in the toolbar, or use the following keyboard shortcuts:
73+
74+
| Action | Keyboard shortcut |
75+
| - | - |
76+
| Go to the previous file in the pull request | **Ctrl**+**Shift**+**Alt**+**F6** |
77+
| Go to the next file in the pull request | **Ctrl**+**Alt**+**F6** |
78+
| Go to the previous comment | **Ctrl**+**Shift**+**Alt**+**F8** |
79+
| Go to the next comment | **Ctrl**+**Alt**+**F8** |
80+
6081
## Next steps
6182

6283
To continue your journey, visit the [Fetch, pull, and sync in Visual Studio](git-fetch-pull-sync.md) page.
Loading
Loading
Loading

0 commit comments

Comments
 (0)