Better MessageBox

[Andrej123456789]

MessageBox is design is kind of Windows 9.x era.
Please add better design at MessageBox.

Example - WPF:

Example - WinForms:

WinForms's MessageBox is much better.

[lindexi]

But we can use the WinForms's MessageBox in WPF.

[ThomasGoulet73]

@Andrej123456789 MessageBox is just a wrapper around the Win32 control. WPF does not control the styling inside the MessageBox. You need an app mainfest to use the more modern controls.

Content of app.manifest:

<?xml version="1.0" encoding="utf-8"?>
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependency>
    <dependentAssembly>
      <assemblyIdentity
          type="win32"
          name="Microsoft.Windows.Common-Controls"
          version="6.0.0.0"
          processorArchitecture="*"
          publicKeyToken="6595b64144ccf1df"
          language="*"
        />
    </dependentAssembly>
  </dependency>
</assembly>

WinForms seems to work without the need for an app manifest (My guess is that it comes from this line: https://github.com/dotnet/winforms/blob/main/src/System.Windows.Forms/src/System/Windows/Forms/MessageBox.cs#L388). It would be interesting to try to add in WPF the code from WinForms that fixes this.

[ClosetBugSlayer]

WPF should be using TaskDialog not MessageBox. Every supported version of Windows has this API now.

[psmulovics]

https://docs.microsoft.com/en-us/windows/win32/controls/task-dialogs

[RussKie]

Windows Forms SDK provides an app.manifest by default, so the comctl 6.0 is used by default as well (with the ubiquitous Appplication.UseVisualStyles() call in Program.cs).
I don't know if WPF provides a default manifest, so this is something to check.

[RussKie]

WPF should be using TaskDialog not MessageBox. Every supported version of Windows has this API now.

It isn't straightforward to correctly use Win32 API, and it requires a lot of elbow grease without managed wrapper (e.g., dotnet/winforms#1133).

[Andrej123456789]

I will try it soon

[ClosetBugSlayer]

It isn't straightforward to correctly use Win32 API, and it requires a lot of elbow grease without managed wrapper (e.g., dotnet/winforms#1133).

The only elbow grease is if you use an activation context, which I do personally just to be safe. Otherwise the default manifest should pull in the API as-is; it works for me in .NET 6 at least.

[Andrej123456789]

@Andrej123456789 MessageBox is just a wrapper around the Win32 control. WPF does not control the styling inside the MessageBox. You need an app mainfest to use the more modern controls.

Content of app.manifest:

<?xml version="1.0" encoding="utf-8"?>
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependency>
    <dependentAssembly>
      <assemblyIdentity
          type="win32"
          name="Microsoft.Windows.Common-Controls"
          version="6.0.0.0"
          processorArchitecture="*"
          publicKeyToken="6595b64144ccf1df"
          language="*"
        />
    </dependentAssembly>
  </dependency>
</assembly>

WinForms seems to work without the need for an app manifest (My guess is that it comes from this line: https://github.com/dotnet/winforms/blob/main/src/System.Windows.Forms/src/System/Windows/Forms/MessageBox.cs#L388). It would be interesting to try to add in WPF the code from WinForms that fixes this.

I tried this but I can't compile project anymore. Here is file so you can check it out.

Here is screenshot of error