ILSpy

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

c-sharp dotnet mono decompile decompiler decompiler-engine dotnetcore ilspy pdb unity

Siegfried Pammer bb1d830ee6 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 stay untouched, so ordinary documents decompile byte-identically. Every BAML stream of an assembly lives in one .resources container, and the recovery around resource writing sat outside the loop over its entries, so a single page that could not be written discarded every other page sharing the container with it. Assisted-by: Claude:claude-opus-5:Claude Code		2 weeks ago
..
ILSpy.BamlDecompiler.Tests.csproj	Fix #2040 : escape BAML strings that XML cannot represent	2 weeks ago
InvalidXmlCharacterTests.cs	Fix #2040 : escape BAML strings that XML cannot represent	2 weeks ago
MissingReferencesTests.cs	Revive BAML decompiler tests as two projects and run them in CI	2 months ago
XmlNamespaceResolutionTests.cs	Fix #1688 : resolve elements to the XML namespace the document declares	2 weeks ago
packages.lock.json	Update NuGet packages; adapt to Dock.Serializer.SystemTextJson 12.1.0.6	3 weeks ago