WinForms Designer Code Rules

The WinForms Designer generates serialization code, not regular C# code. Understanding and following these rules is CRITICAL for Designer compatibility. All WinForms Forms and UserControls should be Designer-compatible — these rules are not optional guidance but mandatory constraints for any code that the Designer must be able to round-trip (read, modify, and re-serialize).

When to Use This Skill

Use this skill when:

• Generating the code which makes up a Form or a UserControl in WinForms.
• Writing or modifying .Designer.cs or .Designer.vb files
• Creating user controls that need Designer support
• Reviewing Designer-generated code
• Reviewing whether WinForms Forms/UserControls are "designed according to standard", "not designed properly", or similar; pair this with managing-winforms-high-dpi-layout so both Designer serialization and human/layout/DPI quality are checked.
• Debugging Designer-related issues
• Migrating forms between .NET Framework and .NET
• Migrating VB6 Code to either Visual Basic (.NET) or C# WinForms Projects.

IMPORTANT: Other skills (layout, rendering, data binding, MVVM) describe what to build. This skill defines how the Designer code-behind file must be structured. When those skills show control configuration, the actual property assignments belong in InitializeComponent following the rules below.