ILSpy

.NET Decompiler with support for PDB generation, ReadyToRun, Metadata (&more) - cross-platform!

Siegfried Pammer 0e09cf3d3e Fix #2040 : escape BAML strings that XML cannot represent Obfuscators put arbitrary characters into BAML strings, and XML 1.0 has no representation for most control characters - a numeric character reference is invalid for them too. Writing such a document threw ArgumentException from XmlWriter, which loses the resource on project export and shows an exception instead of the page in the UI. The escapes are spelled the way the C# output spells them, so one convention covers both languages. Namespace URIs have to be escaped where the XNamespace is created rather than in the final pass: the URI is baked into every element name built from it, so patching only the xmlns declaration would desync the two. Characters XML can carry - tab, newline, astral characters - stay untouched, so ordinary documents decompile byte-identically. Assisted-by: Claude:claude-opus-5:Claude Code		2 weeks ago
..
AttributeRewritePass.cs	Fix #3689 : Only move properties with setters to XAML attributes	6 months ago
ConnectionIdRewritePass.cs	Fix #3318 : missing x:FieldModifier in BAML decompiler	11 months ago
DocumentRewritePass.cs	dev: Strip BOM mark from text files	1 year ago
EscapeInvalidXmlCharactersRewritePass.cs	Fix #2040 : escape BAML strings that XML cannot represent	2 weeks ago
MarkupExtensionRewritePass.cs	dev: Strip BOM mark from text files	1 year ago
XClassRewritePass.cs	dev: Strip BOM mark from text files	1 year ago