[Proposal] Streamline application configuration and bootstrap

[RussKie]

Moved to dotnet/designs#223

[RussKie]

Updated dpi resolution algorithm.

[RussKie]

Progress update:

[omariom]

If the WinForms related properties were prefixed with "WinForms." it would be easier to differentiate them from others
msbuild properties.
Like

  <PropertyGroup>
    <WinForms.ApplicationManifest>app1.manifest</WinForms.ApplicationManifest>
    <WinForms.ApplicationVisualStyles>true</WinForms.ApplicationVisualStyles>
    <WinForms.ApplicationFontName>Control.DefaultFont</WinForms.ApplicationFontName>
    <WinForms.ApplicationFontSize>9</WinForms.ApplicationFontSize>
    <WinForms.ApplicationHighDpiMode>PerMonitorV2</WinForms.ApplicationHighDpiMode>
  </PropertyGroup>

[jnm2]

@omariom I've also seen people make their tooling consume XML property content similar to this:

​  <PropertyGroup>
    <WinForms>
      <ApplicationManifest>app1.manifest</ApplicationManifest>
      <ApplicationVisualStyles>true</ApplicationVisualStyles>
      <ApplicationFontName>Control.DefaultFont<ApplicationFontName>
      <ApplicationFontSize>9<ApplicationFontSize>
      <ApplicationHighDpiMode>PerMonitorV2</ApplicationHighDpiMode>
    </WinForms>
  </PropertyGroup>

[RussKie]

If the WinForms related properties were prefixed with "WinForms." it would be easier to differentiate them from others
msbuild properties.

There are other existing "Application*" properties (e.g. ApplicationIcon and ApplicationManifest, and the new properties will align with those.

[kirsan31]

#4978 triggers me: do we need ApplicationFontStyle here too?

[RussKie]

#4978 triggers me: do we need ApplicationFontStyle here too?

In my opinion this starts encroaching into theming/styling territory. AFAIK Windows has never had a default font that was italic or bold.
SetDefaultFont API was added in response to the changes of the hardcoded default font, and only for the purpose of unblocking and enabling migrations of .NET Framework apps with pixel-perfect layouts. Our goal is to allow building Windows native apps, and whilst the API can now be used beyond the intended use case allowing making Windows apps that don't look native on Windows (and that includes italic or bold fonts) starts working against that goal.
To me personally allowing to make an application default font is a feature request, which probably/arguably has no valid use case behind it.

Happy to continue this discussion.

[Amy-Li03]

This issue is still reproducing on .NET 6.0 latest build: 6.0.100-rc.1.21424.1, as discussed in #5071, need other change merged into, so move Milestone to 6.0 RC2.

[Philip-Wang01]

Verified this issue with .NET 6.0 RC2 latest build: 6.0.10-rc.2.21429.3, Streamline application configuration and bootstrap have been implemented

[Amy-Li03]

Verified this issue with TP build: 6.0.100-rc.1.21453.13, this issue has been fixed.