Repository navigation
feat(diagnostics): ✨ Explain contextual Windows and installer codes - #152
Merged
PrzemyslawKlys merged 2 commits intoOct 9, 2026
Merged
PrzemyslawKlys merged 2 commits into
PrzemyslawKlys merged 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Numeric diagnostic results now explain a bounded set of common Win32, HRESULT and Windows Installer codes with a documented symbolic name, a deterministic description and a concrete next check. Unknown families and application-defined process exits retain their original representation without borrowing another API's meaning.
Application findings include the installer interpretation declared by the captured line. Saved investigations preserve that structured interpretation through inspection and reopening; replay retains the same result for unchanged evidence. Success and restart requirements remain distinct from completed deployment.
The catalog stays in the EventViewerX core and adds no dependencies. Raw captured messages remain excluded from HTML by default.
This PR builds on the captured-investigation workflow in #150. Merge #150 before this layer.
Validation: 68 focused cases pass on each of .NET 8 and 10; all four core targets and the CLI build without warnings or errors. Actual CLI code interpretation and capture/inspect/replay pass with repository fixture forms, and the command passes on PowerShell 5.1 and 7.6.6 using an unsigned validation module. One independent review and a targeted confirmation covered the new contracts. These checks qualify offline fixtures and documented commands; they do not establish live deployment coverage.