pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
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
Siegfried Pammer	d8dfbec04b	Write XAML a XAML parser can read back Two of the defects reported on issue #2253 come from the decompiler writing text that means something else when it is read again. A markup extension is written as a single attribute value, and its grammar gives ',' '=' '{' '}' and the quote characters a meaning. Values went out unquoted, so an argument carrying any of them was read back as further name/value pairs: {DXBinding Expr='Price - Prev > 0 ? ...'}, the reported case, no longer compiles at all (MC3042, MC3045). Values without such a character stay unquoted, because quoting them would rewrite every document that never needed it. A clr-namespace declaration names the CLR namespace it maps, but nothing read that name out of it, so no lookup by namespace could match a declaration the document itself had made. Every type in such a namespace then got a second prefix declared on the element that used it. The assembly is the second half of the same lookup, and there the document records the name it was written against while a well-known type carries the assembly it resolves to now - "mscorlib" against "System.Private.CoreLib" - so the two are also accepted as the same when the recorded assembly forwards the type. Assisted-by: Claude:claude-opus-5:Claude Code	2 weeks ago
Peter Crabtree	e1e16b64f5	dev: Strip BOM mark from text files	1 year ago
Christoph Wille	7c259a8895	Split Baml Addin into library & addin projects	3 years ago