[suggestion] move Dispose(bool disposing) from Form1.Designer.cs to Form1.cs

Issue description

What do you think about moving this method for newly created form? This will save a few seconds of time for each form 😃 But most importantly It’s location raises many questions for beginners (ppl afraid to modify anything in *.Designer.cs): https://stackoverflow.com/questions/1052147/how-do-i-extend-a-winforms-dispose-method https://stackoverflow.com/questions/672980/dispose-on-user-controls-really-meant-to-edit-the-designer-cs-file https://stackoverflow.com/questions/4382693/when-modifying-disposebool-in-a-winforms-generated-designer-cs-file-is-it-nec and so on…

Also it can be modernize a bit.

protected override void Dispose(bool disposing)
{
    if (disposing && (components != null))
    {
        components.Dispose();
    }
    base.Dispose(disposing);
}

To

protected override void Dispose(bool disposing)
{
    if (disposing)
    {
        components?.Dispose();
    }

    base.Dispose(disposing);
}

Or are we afraid that this method will simply be deleted, or corrupted by the user?

[merriemcgaw]

We’ll take this up internally, and explore whether or not this is the right way to ensure that our components are disposed. In general, we like this idea and just want to think about it 😄

[elachlan]

I think this would be more correct than what we have now for the new form template. Its not “generated” code and isn’t updated as far as I know. It would allow easier visibility on what is happening. The *designer.cs hides implementation from users to a degree and this makes it harder to learn the lifecycle.