2

I am trying to use PerMonitorV2 DPI awareness, which resizes non-client area when DPI is changed. MSDN documentation recommends using manifest to set DPI awareness mode: Setting the default DPI awareness for a process.

Manifest Tool section of VS Configuration Properties provides only three options for DPI Awareness: None (unaware), Hight DPI Aware, and Per Monitor DPI Aware (which seems to be PerMonitorV1), so I need to find some way to override those DPI settings, but I don't know how to do that. (My best guess is to somehow provide my own manifest file instead of relying on Visual Studio to generate one.)

πάντα ῥεῖ
  • 1
  • 13
  • 116
  • 190
krsi
  • 1,045
  • 2
  • 14
  • 24
  • you can not use manifest tool and embeded manifest at all. you can direct include your custom manifest in *.rc* file. manifest this is resource. – RbMm Sep 17 '18 at 18:14
  • simply include `CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST "your file.manifest"` to *rc* direct or indirect (say via *.rc2*) and off option embeded manifest in project settings – RbMm Sep 17 '18 at 18:17
  • 2
    Possible duplicate of [How to add a manifest file to a project in visual studio 2010?](https://stackoverflow.com/questions/11504732/how-to-add-a-manifest-file-to-a-project-in-visual-studio-2010) – RbMm Sep 17 '18 at 18:22
  • 2
    It is also possible to use manifest fragments by specifying an entry in the "Additional manifest files" line. Files listed there are basically combined in order to create the final manifest. – SoronelHaetir Sep 17 '18 at 21:16

1 Answers1

3

Within the manifest tool settings, you can define an additional manifest snippet that Visual Studio will merge with the default one. The default manifest will still provide the <dpiAware> tag, to serve as the fallback for older versions of the OS that don't understand the <dpiAwareness> tag.

Steps:

  1. Open project configuration, select "Manifest Tool" > "Input and Output".

  2. In the field "Additional Manifest Files", enter the filename of the manifest snippet you want to include. The path is relative to your project folder.

    The snippet looks like this. Note that I removed the <dpiAware> tag from the MSDN sample:

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2</dpiAwareness>
    </windowsSettings>
  </application>
</assembly>

  3. From the "DPI Awareness" combobox select "High DPI Aware". As written above, this is the fallback value for older Windows versions.

Result:

This is the merged manifest for a Win32 project I created using the application wizard. It is embedded in the resources of the application.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>
  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
      <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2</dpiAwareness>
    </windowsSettings>
  </application>
</assembly>

If you get two <dpiAware> tags, you forgot to remove the <dpiAware> from the manifest snippet.

zett42
  • 25,437
  • 3
  • 35
  • 72