ILSpy

9743 Commits

54 Branches

94 Tags

91 MiB

Tree: 91e9592353

Commit Graph

Author	SHA1	Message	Date
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
Siegfried Pammer	16737cc582	Convert BAML to XAML when exporting a project from the command line A WPF assembly keeps its windows and pages as BAML, so a project exported without converting them back is missing the parts that make it a WPF application - and the reader has no XAML to look at either. The CLI could do the conversion since --decompile-baml was added, but only if asked, which meant that everything the project exporter learned about WPF (Page and ApplicationDefinition items, resources, generated members removed from the code-behind) was invisible to anyone following issue #2253 from the command line. The flag is kept and ignored: it is documented and scripted against, and asking for what is now the default has to keep working. The test fixture is a real .g.resources container rather than a directly embedded .baml stream, because only entries inside a container reach WriteResourceToFile - a standalone .baml is copied out untouched, which is worth its own look. Assisted-by: Claude:claude-opus-5:Claude Code	2 weeks ago

Author

SHA1

Message

Date

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

Siegfried Pammer

16737cc582

Convert BAML to XAML when exporting a project from the command line

A WPF assembly keeps its windows and pages as BAML, so a project exported
without converting them back is missing the parts that make it a WPF
application - and the reader has no XAML to look at either. The CLI could
do the conversion since --decompile-baml was added, but only if asked,
which meant that everything the project exporter learned about WPF (Page
and ApplicationDefinition items, resources, generated members removed
from the code-behind) was invisible to anyone following issue #2253 from
the command line.

The flag is kept and ignored: it is documented and scripted against, and
asking for what is now the default has to keep working.

The test fixture is a real .g.resources container rather than a directly
embedded .baml stream, because only entries inside a container reach
WriteResourceToFile - a standalone .baml is copied out untouched, which
is worth its own look.

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

2 weeks ago

2 Commits (91e9592353d908adf5e9b3bcdfaff53fc65b5aa2)