Skip to content

Commit d22cb91

Browse files
committed
fixes
1 parent 863cd3b commit d22cb91

File tree

2 files changed

+0
-13
lines changed

2 files changed

+0
-13
lines changed

docs/javascript/tutorial-asp-net-core-with-react.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -119,15 +119,7 @@ Make sure to install the following:
119119
>[!NOTE]
120120
> Check console output for messages, such as a message instructing you to update your version of Node.js.
121121
122-
<<<<<<< HEAD
123-
<<<<<<< HEAD
124-
You should see an React app appear, that is populated via the API. If you don't see the app, see [Troubleshooting](#troubleshooting).
125-
=======
126122
You should see a React app appear, that is populated via the API. If you don't see the app, see [Troubleshooting](#troubleshooting).
127-
>>>>>>> e544f53505bc3ae40a8373f51b01c45500805bfa
128-
=======
129-
You should see a React app appear, that is populated via the API. If you don't see the app, see [Troubleshooting](#troubleshooting).
130-
>>>>>>> 8bee33d8bd3bd4ad0353717553013d252b3e61f9
131123

132124
## Publish the project
133125

docs/profiling/profiling-feature-tour.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -184,7 +184,6 @@ The tool shows each async operation in a list view. You can see information such
184184

185185
![.NET Async Tool Stopped](../profiling/media/vs-2022/prof-tour-async-tool.png ".NET Async Tool Stopped")
186186
::: moniker-end
187-
188187
::: moniker range="vs-2019"
189188
## Analyze asynchronous code (.NET)
190189

@@ -195,8 +194,6 @@ The tool shows each async operation in a list view. You can see information such
195194
![.NET Async Tool Stopped](../profiling/media/async-tool-opened.png ".NET Async Tool Stopped")
196195
::: moniker-end
197196

198-
::: moniker range=">=vs-2019"
199-
200197
## Examine application events
201198

202199
The generic [events viewer](../profiling/events-viewer.md) allows you to view the activity of your application through a list of events, such as module load, thread start, and system configurations, to help better diagnose how your application is performing right within the Visual Studio profiler. This tool is available in the Performance Profiler. Open the Performance Profiler by choosing **Debug** > **Performance Profiler** (or **Alt + F2**).
@@ -233,8 +230,6 @@ The tool shows live values for each counter in a list view.
233230

234231
:::image type="content" source="../profiling/media/dotnet-counters-tool-collecting.png" alt-text=".NET Counter tool collecting.":::
235232

236-
::: moniker-end
237-
238233
## Analyze resource consumption (XAML)
239234

240235
In XAML apps, such as Windows desktop WPF apps and UWP apps, you can analyze resource consumption using the Application Timeline tool. For example, you can analyze the time spent by your application preparing UI frames (layout and render), servicing network and disk requests, and in scenarios like application startup, page load, and Window resize. To use the tool, choose **Application Timeline** in the Performance Profiler, and then choose **Start**. In your app, go through the scenario with a suspected resource consumption issue, and then choose **Stop collection** to generate the report.

0 commit comments

Comments
 (0)