Log Viewer (Log4j, NLog) Files

LogViewer 1.2.9.0

Download LogViewer-1.2.9.0.zip below, extract it to any folder you can write to and run LogViewer.exe. Requires .NET Framework 4.8 (included in Windows 10 1903+ and Windows 11). Settings in Documents\LogViewer are kept.

The executable is not code-signed, so Windows SmartScreen may warn on the first start: choose More info -> Run anyway.

New

• Updates from GitHub Releases: shortly after start the application checks for a new version and offers to update, remind you later or skip that version
• The update is downloaded with a checksum check and installed over the current folder, then the application restarts; settings.xml and logs next to the exe are left untouched
• You can save the session before updating: the log buffer is kept only in memory
• "Check for updates at startup" setting; the "Check for updates" button checks on demand, including a skipped version

Changed

• The Release Notes window is shown on the first start of a new version, not only after a ClickOnce update
• ClickOnce is no longer used. Versions before 1.2.9.0 cannot update themselves: download the new version once by hand
• Find next and previous, jumping to the next error or warning, and going to a timestamp no longer copy the whole list: with large buffers they respond at once, even while logs are being received
• A log line in the list uses less memory: its data is no longer duplicated between the buffer and the list
• Receiving logs, the repeats window, and filtering with a search put less load on the CPU and memory

Fixed

• Settings, sessions, filter presets and import templates are saved so that a failure during the write no longer leaves a truncated file or resets the configured receivers
• If the settings file cannot be read, the application warns about it and keeps a copy instead of silently replacing it with defaults
• An ignored IP address hides only that address: the rule 10.0.0.1 no longer hides 10.0.0.10–10.0.0.19 and 110.0.0.1
• Files from folders with spaces in the path open via "Open with" when LogViewer is already running
• TCP: an event written as a self-closing tag no longer swallows the next event, and inside CDATA no longer cuts the message
• TCP: large events (for example, with a long stack trace) are received without excessive CPU load
• A parse error row keeps only the start of the original XML: a stream of malformed messages no longer bloats memory