She could manually hunt for the bug, but that meant scanning thousands of lines of nested <Transaction> , <Party> , and obscure <AdjustmentReasonCode> tags. Or she could spin up a Linux VM and wait 15 minutes.
She opened a new file— xmllint_notes.txt —and wrote: For future me: xmllint.exe + libxml2.dll + libiconv2.dll + zlib1.dll. Keep them in version control under /tools. They will save your night someday. Then she added a PowerShell function to her profile: xmllint for windows
Instead, Priya opened her browser and searched: “xmllint for windows.” She could manually hunt for the bug, but
.\xmllint --valid .\config.xml 2>&1 | Select-String "error" The output hit like a puzzle piece clicking into place: and obscure <
xmllint: using libxml version 20914 It worked.
.\xmllint --version The terminal blinked. Then:
Priya ran the validation: