How do I make the Windows Forms Designer experience similar to previous .NET Framework versions, in terms of reliability and performance?

Matteo Bagattini 76 Reputation points

Windows Forms designer experience (VS 17.7.4 but also previous versions) is being lacklustre moving on after .NET Framework. I'm migrating a small application that was using .NET Framework 4.8 to .NET 6 and I'm constantly battling with Visual Studio to make it work. Some problems are:

  • The designer is slow to load
  • When I copy (CTRL+C) a control, it works for several seconds before returning ready
  • Often, the toolbox doesn't load the controls
  • Often, the properties window doesn't show the selected control properties

I have to close/reopen the designer tabs or kill the devenv process, reload and cross my fingers.

In this case I'm migrating a small solution, but I'll soon need to migrate a much larger codebase and I'm pretty terrified about the prospect.

Is there anything I can do to make the designer more stable, reliable and reactive?

Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
3,770 questions
{count} vote