ILSpy

94 Tags

91 MiB

Tree: 199b7bf151

Author	SHA1	Message	Date
Siegfried Pammer	fceb892cb3	Keep BAML decompilation working when WPF assemblies are missing KnownThings hard-required PresentationFramework, PresentationCore and WindowsBase to be resolvable, so decompiling a WPF binary on a machine without WPF (Linux/macOS) threw "Could not resolve known assembly" and aborted the whole BAML decompile. Mirror MinimalCorlib: when a well-known BAML assembly cannot be resolved, BamlDecompilerTypeSystem substitutes a synthetic stand-in module that upholds the invariant KnownThings assumes. The stand-in only materializes the types the decompiler explicitly seeds, so it stays bounded to the well-known set and references to other types keep degrading to UnknownType exactly as before. For the WPF assemblies it also reproduces the XmlnsDefinitionAttribute mapping so known types still serialize under the presentation xmlns instead of a clr-namespace fallback. Assisted-by: Claude:claude-opus-4-8:Claude Code	2 months ago
Peter Crabtree	e1e16b64f5	dev: Strip BOM mark from text files	1 year ago
Siegfried Pammer	ca78d4a14d	Use MetadataFile instead of PEFile in TypeSystem.	3 years ago
Christoph Wille	7c259a8895	Split Baml Addin into library & addin projects	3 years ago
SilverFox	a917690fdf	Fix null check in BamlDecompilerTypeSystem.HasType	5 years ago
Siegfried Pammer	113e00505d	Fix #2337 : Expose simple public XamlDecompiler API.	5 years ago