Application executable is not marked as Windows 10 compatible in the default manifest

The manifest of self-contained apps does not contain Windows 10 supportedOS element. It means that self-contained applications run with compatibility shims by default.

The proposal based on the offline discussion:

• Stop embedding the manifest in Roslyn for .NET 5 by passing the right command line option to the C# compiler (-nowin32manifest). There is a MS build property that drives this that we should set by default for .NET 5+, unless the app has explicitly provided manifest.
  • This is going to make apps on Linux a bit smaller. The Windows manifest in app.dll is a dead weight on Linux.
• Attach Win10 compatible manifest to apphost by default if there is not one in app.dll.

Related:

• https://github.com/dotnet/runtime/pull/33651
• https://github.com/dotnet/core-setup/pull/4700
• https://github.com/dotnet/runtime/issues/3028

[agocke]

@mateoatr Could you take a look at this?

[miloush]

Thanks, I think it would be good to have the default manifest updated. Doesn’t have to be for .NET 8 obviously, but comctl6 is supported on all Windows versions supported by .NET, and Windows 10 is the only supported OS since .NET 7. Not quite sure why that is not reflected in the default manifest. For WPF we could add a build task to patch the default manifest during compilation, but I was interested first why shouldn’t everyone simply have a better manifest out of the box.