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 bff069a9e2 Put a XAML document where its code-behind is The project exporter wrote every XAML document to the project root under a fully-qualified name while the code-behind class went into a directory named after its namespace, so the two halves of one partial class ended up in different places. WPF tooling pairs MainWindow.xaml with MainWindow.xaml.cs by name and location; anything else is an unrelated file to it, and --nested-directories made the split wider still by moving only the C# half. Both now go through one function that decides where a type's files live, so the document lands where the type's own C# file would have, and the code-behind is named after the document. The BAML writers of the UI and of the command line had grown their own copies of the naming, which is how they came to disagree with the C# writer in the first place. Assisted-by: Claude:claude-opus-5:Claude Code		2 weeks ago
..
IProjectFileWriter.cs	Publicize `IProjectFileWriter` implementations (#3934 )	2 months ago
IProjectInfoProvider.cs	Provide a WholeProjectDecompiler constructor with no default parameter values	2 months ago
ProjectFileWriterDefault.cs	Publicize `IProjectFileWriter` implementations (#3934 )	2 months ago
ProjectFileWriterSdkStyle.cs	#3315 : Gate implicit references the way the SDK gates them	2 weeks ago
TargetFramework.cs	dev: Strip BOM mark from text files	1 year ago
TargetServices.cs	#3315 : Keep the target platform in exported target framework monikers	2 weeks ago
WholeProjectDecompiler.cs	Put a XAML document where its code-behind is	2 weeks ago