Since it is just Windows API, I think it will be faster to write in C++ than in Assembly

Also, the FASM program with just a dialog box takes about 2Kb, but the C/C++ code of same nature may be larger.

#include <windows.h>
#include <winuser.h>

void Show(wchar_t *cap, wchar_t *mes, int ico) {
    HWND hWnd = GetForegroundWindow();
    MessageBoxW(hWnd, mes, cap, ico);
}

void Usage() {
    Show(L"Внимание!",
    L"Использование:\n\nMessageShow.exe <заголовок> <сообщение> [цифра-иконки]\n\n"
    "Цифра иконки (если не указана, то: Information)\n\n"
    "  1 Exclamation\n"
    "  2 Warning\n"
    "  3 Information\n"
    "  4 Asterisk\n"
    "  5 Question\n"
    "  6 Stop\n"
    "  7 Error\n"
    "  8 Hand\n\n",
    MB_ICONINFORMATION | MB_OK);
}

INT WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, INT nCmdShow) {
    wchar_t** szArglist;
    int nArgs;
    szArglist = CommandLineToArgvW(GetCommandLineW(), &nArgs);
    if (NULL == szArglist) {
        Usage();
        return 0;
    } else {
        if (nArgs < 3) {
            Usage();
        } else {
            int ico = 0;
            if (nArgs > 3) {
                if (lstrcmpW(szArglist[3], L"1") == 0) {
                    ico = MB_ICONEXCLAMATION;
                }
                if (lstrcmpW(szArglist[3], L"2") == 0) {
                    ico = MB_ICONWARNING;
                }
                if (lstrcmpW(szArglist[3], L"3") == 0) {
                    ico = MB_ICONINFORMATION;
                }
                if (lstrcmpW(szArglist[3], L"4") == 0) {
                    ico = MB_ICONASTERISK;
                }
                if (lstrcmpW(szArglist[3], L"5") == 0) {
                    ico = MB_ICONQUESTION;
                }
                if (lstrcmpW(szArglist[3], L"6") == 0) {
                    ico = MB_ICONSTOP;
                }
                if (lstrcmpW(szArglist[3], L"7") == 0) {
                    ico = MB_ICONERROR;
                }
                if (lstrcmpW(szArglist[3], L"8") == 0) {
                    ico = MB_ICONHAND;
                }
            }
            HWND hWnd = GetForegroundWindow();
            MessageBoxW(hWnd, szArglist[2], szArglist[1], ico|MB_OK|MB_TOPMOST);
        }
        LocalFree(szArglist);
    }
    return 0;
}    

    E:\Tools\MSys64\mingw32\bin\gcc.exe ^
      -D UNICODE -D _UNICODE ^
      -s -Os -fno-ident -fno-stack-protector -fomit-frame-pointer ^
      -fno-unwind-tables -fno-asynchronous-unwind-tables -falign-functions=1 ^
      -e _WinMain ^
      -Wl,--enable-stdcall-fixup ^
      -nostdlib -nodefaultlibs -nostartfiles -o MessageShow.exe main.c -lkernel32 -luser32 -lshell32    

Quote:

Guys, since I gave up using dialog boxes long ago due to the quirks with fonts and font-relative sizing, may I ask you how in general do you build dialog-based interfaces with Per-Monitor High DPI support? I mean, it definitely should be possible, but I seem to be too lazy to figure out how to build things up together to ensure it looks properly everywhere. Arbitrary font properties, resizing controls at runtime based on current dialog size, adjusting it to monitor DPI, etc.

D2D1RenderTarget