You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ide/visual-studio-whole-line-completions.md
+31-4Lines changed: 31 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -46,13 +46,19 @@ When the user has an item from the IntelliSense list selected, IntelliCode uses
46
46
47
47
### Accept or dismiss whole-line autocompletions
48
48
49
-
By default, the `Tab` key is used to accept whole-line autocompletions. To change the default accept key, go to Tools -> Options -> IntelliCode -> Completions for whole lines of code. Enable the setting named `Apply completions for whole lines on right arrow`.
49
+
By default, the `Tab` key is used to accept whole-line autocompletions. To change the default accept key to the right arrow, go to **Tools** > **Options** > **IntelliCode** -> **Advanced**.
50
50
51
-
52
-
53
-
Doing so changes the accept key from `Tab` to the right arrow `->`
51
+
:::moniker range="<=vs-2019"
52
+
Enable the setting named `Apply completions for whole lines on right arrow`.
54
53
55
54
55
+
:::moniker-end
56
+
57
+
:::moniker range=">=vs-2022"
58
+
Enable the setting `Apply whole line completions on right arrow`.
59
+
60
+
61
+
:::moniker-end
56
62
57
63
To dismiss whole-line autocompletions, the `ESC` or `Delete` keys can be used.
58
64
@@ -64,6 +70,8 @@ To dismiss whole-line autocompletions, the `ESC` or `Delete` keys can be used.
64
70
65
71
You can control the whole-line autocompletions feature using the small purple light bulb shown at the bottom right of the editor, next to the zoom control.
66
72
73
+
:::moniker range="<=vs-2019"
74
+
67
75
68
76
69
77
The first setting, `Show completions for lines of code` allows you to turn whole-line autocompletions on or off.
@@ -72,6 +80,25 @@ The second setting, `Wait for pauses in typing before showing line completions`,
72
80
73
81
The third setting, `Show completions on new lines` can be turned on or off depending on whether you want to see whole-line autocompletions when you enter a new line, that is, by pressing `Return` or `Enter`.
74
82
83
+
:::moniker-end
84
+
:::moniker range=">=vs-2022"
85
+
86
+
In **Tools**, **Options**, **IntelliCode**, **General**, the setting `Show inline completions` allows you to turn whole-line autocompletions on or off.
87
+
88
+
The **Advanced** tab has further options.
89
+
90
+
91
+
92
+
The first setting, `Apply whole line completions on right arrow` was discussed previously in this article.
93
+
94
+
The second setting, `Disable suggestions while debugging` allows you to minimize distractions when debugging.
95
+
96
+
The third setting, `Show inline completions on new lines` can be turned on or off depending on whether you want to see whole-line autocompletions when you enter a new line, that is, by pressing `Return` or `Enter`.
97
+
98
+
The last setting, `Wait for pauses in typing before showing line completions`, when enabled, makes whole-line autocompletions only show up if you pause typing. You might prefer this option if you find the whole-line autocompletions distracting in the default mode.
99
+
100
+
:::moniker-end
101
+
75
102
## Provide feedback
76
103
77
104
Click on the Feedback icon on the top right of Visual Studio to file a feedback ticket. Optionally, you can upload your IntelliCode log files to the feedback ticket in order to provide us with additional context. Make sure you review the contents of the log files and address any privacy concerns you may have. This data, when shared with us, will not be used for any purpose other than providing support assistance to you. You can find the logs at `%LOCALAPPDATA%\Temp\VSFeedbackIntelliCodeLogs`
Copy file name to clipboardExpand all lines: docs/profiling/cpu-insights.md
+7-4Lines changed: 7 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,31 @@
1
1
---
2
2
title: Diagnose high latency with CPU Insights
3
3
description: Use CPU Insights to diagnose and optimize your code's performance
4
-
ms.date: 01/10/2023
4
+
ms.date: 09/06/2024
5
5
ms.topic: how-to
6
6
author: mikejo5000
7
7
ms.author: mikejo
8
8
manager: mijacobs
9
9
ms.subservice: debug-diagnostics
10
10
monikerRange: '>= vs-2022'
11
11
---
12
+
12
13
# Diagnose high latency with CPU Insights
13
14
14
15
CPU insights is a sub-feature of the CPU Usage tool that shows common potential latency issues like concatenating strings inefficiently.
15
16
16
-
## View top insights
17
+
## View Auto Insights
17
18
18
19
The **Top Insights** section in the CPU Usage tool shows quick CPU details, insights, and suggestions in the description so that you can continue diagnosing the issue. The **Learn more** link shows you in-depth documentation that explains your issue. If you need more information, **View source code** shows more details. Once selected, you can see the call tree view, showing the process, functions, and which callers use the most CPU.
19
20
20
-
![Screenshot showing Top Insights selected.](./media/vs-2022/top-insights.png"Top Insights selected")
On the summary page under **Top Functions**, you can find the top functions called with the time spent in descending order. **Total CPU** time is the amount of time spent inside a function, including any functions it calls, whereas **Self CPU** is time spent exclusively in the function.
25
26
27
+
28
+
26
29
## View the hot path
27
30
28
31
**Hot Path** shows where most of the CPU time was being spent in your application and helps focus investigation on the area that would have the most impact. Analyzing this code path by using other tools in the Performance Profiler can help identify ways to improve the code as well. For example, it may help identify how to minimize allocations on the hot path to reduce GC frequency and time spent in GC.
@@ -32,7 +35,7 @@ On the summary page under **Top Functions**, you can find the top functions call
32
35
::: moniker range=">= vs-2022"
33
36
## Get AI assistance
34
37
35
-
If you have [Copilot](../ide/visual-studio-github-copilot-extension.md), you can get AI assistance while you're looking at CPU insights. Just look for the **Ask Copilot** button. In these scenarios, Copilot already knows the context for your questions, so you don't need to provide context yourself in chat. For more information, see [Debug with Copilot](../debugger/debug-with-copilot.md).
38
+
If you have [Copilot](../ide/visual-studio-github-copilot-extension.md), you can get AI assistance while you're looking at CPU Auto Insights. Just look for the **Ask Copilot** button. In these scenarios, Copilot already knows the context for your questions, so you don't need to provide context yourself in chat. For more information, see [Debug with Copilot](../debugger/debug-with-copilot.md).
Copy file name to clipboardExpand all lines: docs/test/microsoft-code-coverage-console-tool.md
+17-15Lines changed: 17 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Microsoft.CodeCoverage.Console tool
3
3
description: Use the Microsoft.CodeCoverage.Console tool to collect code coverage for C++ and C# code in nontest scenarios, and merge and convert code coverage reports.
4
-
ms.date: 04/10/2024
4
+
ms.date: 09/16/2024
5
5
ms.topic: conceptual
6
6
ms.author: mikejo
7
7
manager: mijacobs
@@ -12,7 +12,7 @@ author: mikejo5000
12
12
13
13
Microsoft.CodeCoverage.Console is a command-line tool. You can use it to collect code coverage for C++ and C# code. It supports also merging and converting code coverage reports. This tool can be used to collect code coverage in non-test scenarios (for example, for a simple console application).
14
14
15
-
Microsoft.CodeCoverage.Console is available in Visual Studio 2022 17.3 under folder `Common7\IDE\Extensions\Microsoft\CodeCoverage.Console`. You can use it in a Developer Command Prompt and a Developer PowerShell:
15
+
Microsoft.CodeCoverage.Console is available in Visual Studio 2022 17.3 under the folder `Common7\IDE\Extensions\Microsoft\CodeCoverage.Console`. You can use it in a Developer Command Prompt and a Developer PowerShell:
16
16
17
17
>[!NOTE]
18
18
> The tool is available only with Visual Studio Enterprise. For .NET code coverage, you can alternatively use the command-line tool, [dotnet-coverage](/dotnet/core/additional-tools/dotnet-coverage).
@@ -42,9 +42,11 @@ Commands:
42
42
43
43
## Collect, connect, shutdown, merge and snapshot commands
44
44
45
-
The Microsoft.CodeCoverage.Console tool is extension to the [dotnet-coverage](/dotnet/core/additional-tools/dotnet-coverage) dotnet tool. The documentation for collect, connect, shutdown, merge and snapshot commands can be found [here](/dotnet/core/additional-tools/dotnet-coverage). Additionally, the Microsoft.CodeCoverage.Console tool supports collecting code coverage for C++ code.
45
+
The Microsoft.CodeCoverage.Console tool is extension to the [dotnet-coverage](/dotnet/core/additional-tools/dotnet-coverage) dotnet tool. The documentation for collect, connect, shutdown, merge, and snapshot commands can be found [here](/dotnet/core/additional-tools/dotnet-coverage).
46
46
47
47
::: moniker range=">=vs-2022"
48
+
Starting in Visual Studio 2022, Microsoft.CodeCoverage.Console supports additional security features to enable collecting ASP.NET code coverage data from IIS. Additionally, the Microsoft.CodeCoverage.Console tool supports collecting code coverage for C++ code. The `instrument` command is specific to these scenarios.
49
+
48
50
## Instrument command
49
51
50
52
The instrument command is used to instrument native or managed binary on disk.
> Instrumented native binary contains a reference to `static_covrun64.dll`. Make sure that this file is next to the instrumented binary or the directory where `static_covrun64.dll` is located is listed in the `Path` environment variable. The `collect` and `connect` commands are adding proper directories to `Path` automatically.
0 commit comments