ILSpy

9792 Commits

54 Branches

94 Tags

91 MiB

Tree: 72dbe6f41d

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	1c8a6bb781	Surface recovered export failures in the report the user actually sees An export's ITextOutput goes nowhere: ProjectExporter and SolutionWriter both hand the language a throwaway PlainTextOutput and build their own status report, so a language writing failures into that output is invisible. The failures travel on DecompilationOptions instead and are rendered by the caller that owns the report - each one with its full exception in a collapsed fold, which is what makes a bug report actionable. Drive-by: WriteExceptionDetails split the exception text without trimming, so for exceptions rendering a trailing newline the fold reached one line past the last frame and swallowed the line behind it; and the tab's own decompilation- failure path had regressed to dumping a raw stack trace instead of using that helper. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	1 month ago

Author

SHA1

Message

Date

Siegfried Pammer

1c8a6bb781

Surface recovered export failures in the report the user actually sees

An export's ITextOutput goes nowhere: ProjectExporter and SolutionWriter both
hand the language a throwaway PlainTextOutput and build their own status
report, so a language writing failures into that output is invisible. The
failures travel on DecompilationOptions instead and are rendered by the caller
that owns the report - each one with its full exception in a collapsed fold,
which is what makes a bug report actionable.

Drive-by: WriteExceptionDetails split the exception text without trimming, so
for exceptions rendering a trailing newline the fold reached one line past the
last frame and swallowed the line behind it; and the tab's own decompilation-
failure path had regressed to dumping a raw stack trace instead of using that
helper.

Assisted-by: Claude:claude-opus-5[1m]:Claude Code

1 month ago

1 Commits (72dbe6f41d480728ffa60bb68d1b95f9118d6b15)