Update Winforms C#/VB templates designer code in InitializeComponent() for modernized CodeDom Serialization

.NET version

8.0.100-alpha.1.22607.6

Did it work in .NET Framework?

N/A

Did it work in any of the earlier releases of .NET Core or .NET 5+?

N/A

Issue description

WinForms Designer GH https://github.com/microsoft/winforms-designer/pull/4425 for OutOf-Proc Designer had modernized CodeDom serialization, code for InitializeComponent(), is generated taking into account .editorconfig preferences and <ImplicitUsings>enable</ImplicitUsings> project property. However, Winforms C#/VB templates do not respect these settings.

Template Winforms C# designer code: — need to update After added a button with modernized CodeDom serialized code

Template Winforms VB designer code: — need to update After added a button with modernized CodeDom serialized code

Steps to reproduce

1. Just create a Winforms .Net C#/VB application
2. Go to Form designer file, check the code in InitializeComponent()

[merriemcgaw]

I’m OK changing the templates in .NET 8 to match the new codegen. In fact it looks much cleaner. We’ll do a brag blog to talk about the modern codegen and that should alleviate a lot of the confusion from most people.

[KlausLoeffelmann]

We should do it via .editorconfig, but there will be things, which will not be picked up or be configured. And that’s fine. There will be differences, and ultimately, we will introduce even breaking changes. (Think of NameOf).

That’s what we knew and wanted when @DustinCampbell started the work on it.

The whole point IS to modernize, and introduce modern styles, approaches and paradigms. Let’s please not be afraid of reasonable breaking changes. There will be no confusion for customers, as long, as we’re documenting and reason our changes. @merriemcgaw FYI.