ILSpy

9645 Commits

54 Branches

94 Tags

91 MiB

Branch: fix/lambda-parameter-syntax

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	b5a605e7a8	Honor the user's decompiler settings in all decompilation paths The Avalonia port gave DecompilationOptions a parameterless constructor that silently defaults to new DecompilerSettings(). Several paths picked it up and decompiled with default settings where the WPF version used the user's current options: tree member filtering (CSharpLanguage. ShowMember), PDB generation, the single-file / project / solution Save Code paths, and the DEBUG decompile-all commands. Promote the live-snapshot logic that was private to DecompilerTabPage- Model (settings clone + Display-option bridge + toolbar language version) to SettingsService.CreateEffectiveDecompilerSettings and use it at every entry point. Remove the parameterless DecompilationOptions constructor and make SolutionWriter require settings, so reaching for defaults is an explicit choice rather than a silent fallback - that default is exactly what masked these regressions. Search deliberately keeps default settings (it only needs a type system to materialise). Assisted-by: Claude:claude-fable-5:Claude Code	3 months ago

Author

SHA1

Message

Date

Siegfried Pammer

b5a605e7a8

Honor the user's decompiler settings in all decompilation paths

The Avalonia port gave DecompilationOptions a parameterless constructor
that silently defaults to new DecompilerSettings(). Several paths picked
it up and decompiled with default settings where the WPF version used
the user's current options: tree member filtering (CSharpLanguage.
ShowMember), PDB generation, the single-file / project / solution Save
Code paths, and the DEBUG decompile-all commands.

Promote the live-snapshot logic that was private to DecompilerTabPage-
Model (settings clone + Display-option bridge + toolbar language
version) to SettingsService.CreateEffectiveDecompilerSettings and use
it at every entry point. Remove the parameterless DecompilationOptions
constructor and make SolutionWriter require settings, so reaching for
defaults is an explicit choice rather than a silent fallback - that
default is exactly what masked these regressions. Search deliberately
keeps default settings (it only needs a type system to materialise).

Assisted-by: Claude:claude-fable-5:Claude Code

3 months ago

1 Commits (fix/lambda-parameter-syntax)