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 8747055beb Recover a StartupUri, and leave a type's own Name property alone Two things #2253 costs an exported application, both found by decompiling one that was built from published source. StartupUri is written in App.xaml but never reaches the BAML: the markup compiler turns the attribute into an assignment inside InitializeComponent, and the project decompiler deletes the generated members. The exported application then builds and opens no window. The assignment is read back out of the generated method and written to the document root again. Where the compiler emits no app.baml at all - App.xaml carrying nothing but attributes - there is no document to write it on, and the export has no ApplicationDefinition either; that is a larger gap of its own. x:Name is recorded as the runtime name property of an element, which is FrameworkElement.Name for everything WPF - a property of the framework. Any property called "Name" on a type of the assembly being decompiled was written back as the directive, so <local:Helper Name="theName" /> came back as x:Name: the name gets registered and the property stays unset, which still compiles and quietly means something else. The directive is now written only for a name the element does not declare itself. Assisted-by: Claude:claude-opus-5:Claude Code	2 weeks ago
..
Blocks	dev: Strip BOM mark from text files	1 year ago
Records	Recover a StartupUri, and leave a type's own Name property alone	2 weeks ago

Siegfried Pammer 8747055beb Recover a StartupUri, and leave a type's own Name property alone

Two things #2253 costs an exported application, both found by decompiling
one that was built from published source.

StartupUri is written in App.xaml but never reaches the BAML: the markup
compiler turns the attribute into an assignment inside
InitializeComponent, and the project decompiler deletes the generated
members. The exported application then builds and opens no window. The
assignment is read back out of the generated method and written to the
document root again. Where the compiler emits no app.baml at all -
App.xaml carrying nothing but attributes - there is no document to write
it on, and the export has no ApplicationDefinition either; that is a
larger gap of its own.

x:Name is recorded as the runtime name property of an element, which is
FrameworkElement.Name for everything WPF - a property of the framework.
Any property called "Name" on a type of the assembly being decompiled was
written back as the directive, so <local:Helper Name="theName" /> came
back as x:Name: the name gets registered and the property stays unset,
which still compiles and quietly means something else. The directive is
now written only for a name the element does not declare itself.

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

2 weeks ago

Blocks

dev: Strip BOM mark from text files

1 year ago

Records

Recover a StartupUri, and leave a type's own Name property alone

2 weeks ago