Edit

Share via


XAML Hot Reload and its impact on performance diagnostic in Visual Studio

When you're investigating an application's performance, in other words, its CPU usage and memory consumption, we recommend that you disable XAML Hot Reload. Go to Tools > Options > Debugging > XAML Hot Reload and uncheck Enable XAML Hot Reload.

XAML Hot Reload requires executing special code in a running application to collect more data. It's likely to execute user code and platform code that wouldn't have been executed otherwise. For example, WPF Hot Reload requires the use of the VisualDiagnostics API to find info about an element's location in source *.xaml files. All of this extra code execution can affect collected performance data.

Support options

Here are support resources that you might find useful:

  • Ask a question or find an answer on the Microsoft Q&A page for Visual Studio.
  • Report product issues to the engineering team via the Report a problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE.
  • Track product issues and engineering team responses in the Visual Studio Developer Community.