You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 19, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 19, 2021. It is now read-only.
Fundamental problem that prohibits ILMerge to work with XAML files/resources #92
Hi!, does anybody has have some intuition in why ILMerge can't work with XAML files/resources,
Is it just a matter of taking the initiative (I wonder if I could help), or are there fundamental reasons why the original develop team opt out to do it in the first place?
Not only XAML should be supported, but also its binary variants such as BAML (used in WPF) and WinRT serialization format (Windows Store apps). Those formats are undocumented and need significant efforts in order to be supported.
I mean literally man/years if you do it from scratch or maybe a bit less if you use existing efforts as a starting point.
Activity
hrumhurum commentedon Sep 16, 2020
XAML remastering is a tough task to undertake.
Not only XAML should be supported, but also its binary variants such as BAML (used in WPF) and WinRT serialization format (Windows Store apps). Those formats are undocumented and need significant efforts in order to be supported.
I mean literally man/years if you do it from scratch or maybe a bit less if you use existing efforts as a starting point.