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
When I add a UWP reference to a .NET 6.0 project Visual Studio gets very slow and uses all my CPUs.
Repro steps
I've started a hobby project to control my standing desk via Bluetooth. The source can be found here: https://github.com/toburger/IdasenDesk
In order to work with Bluetooth I need to access the Windows.Devices.Bluetooth namespace, which is part of the Universal Windows Platform (UWP).
When I open the project in Visual Studio and start to edit the code Visual Studio eats all of my CPU and Intellisense gets unresponsive.
Expected behavior
"Normal" Visual Studio development experience.
Actual behavior
Intellisense gets unresponsive after editing code unless I rest for a while and let Visual Studio catch up.
toburger
changed the title
UWP Visual Studio development experience: high CPU usage and Intellisense unresponsive
[UWP] Visual Studio development experience: high CPU usage and Intellisense unresponsive
May 31, 2022
When I add a UWP reference to a .NET 6.0 project Visual Studio gets very slow and uses all my CPUs.
Repro steps
I've started a hobby project to control my standing desk via Bluetooth. The source can be found here: https://github.com/toburger/IdasenDesk
In order to work with Bluetooth I need to access the
Windows.Devices.Bluetooth
namespace, which is part of the Universal Windows Platform (UWP).When I open the project in Visual Studio and start to edit the code Visual Studio eats all of my CPU and Intellisense gets unresponsive.
Expected behavior
"Normal" Visual Studio development experience.
Actual behavior
Intellisense gets unresponsive after editing code unless I rest for a while and let Visual Studio catch up.
Known workarounds
Just be patient. 😉
Related information
Provide any related information (optional):
The text was updated successfully, but these errors were encountered: