Skip to content

fix nested Type names in BAML -> XAML decompile#3

Merged
glenn-slayden merged 2 commits intomasterfrom
patch-1
Apr 25, 2023
Merged

fix nested Type names in BAML -> XAML decompile#3
glenn-slayden merged 2 commits intomasterfrom
patch-1

Conversation

@glenn-slayden
Copy link
Copy Markdown
Owner

@glenn-slayden glenn-slayden commented Apr 25, 2023

Nested Type names were quite broken. Of course they are doomed in XAML anyway, but this solves a fair about of the corruption and crashing-out-of-decompile problems.

Examples now much improved:
System.Activities.Presentation.View.TypeBrowser
System.Activities.Core.Presentation.FlowchartDesigner
System.Activities.Presentation.View.VBIdentifierDesigner

use '+' when decompiling from BAML to XAML when some MarkupExtensions contain nested Type names e.g.

System.Activities.Presentation.View.VBIdentifierDesigner ...

--> "{x:Static sad:WorkflowDesignerIcons+DesignerItems.WarningValidation}"
Nested Type names were quite broken.  Of course they are doomed in XAML anyway, but this solves a fair about of the corruption and crashing-out-of-decompile problems.

Examples now much improved:
System.Activities.Presentation.View.TypeBrowser
System.Activities.Core.Presentation.FlowchartDesigner
@glenn-slayden glenn-slayden merged commit f8891c2 into master Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant