Steven Brix

> I'm not really familiar with type metadata that's available for C++, but if it has types, properties, methods and enums in a form that is easily accessible from C#...

As I mentioned before (https://github.com/AvaloniaUI/Avalonia/pull/2734#issuecomment-540664816) we want to make a more modular XAML compiler. We haven't started working on anything, so I'm very glad I reached out to you guys...

You're AST looks fairly similar to what our node streams look like today, but I'm not our XBF/Compiler expert though, so I'll let @alwu-msft comment on that. We don't use...

> I understand that switching out the backend to produce XBF/BAML does effectively remove have the compiler from play, but I think it's a necessary thing to do for v1...

@worldbeater just to be clear, I want to keep this conversation going, but I'm not able to make any guarantees at the moment because we really need to focus on...

> There doesn't appear to be anything we can do about this, as the selection of the WPF designer is done in core VS before anything in our extension is...

> Here is a link to the "language server" we use for avalonia... Plus plus! What does your language server do, is it just intellisense and auto-completion, or does it...

> Custom controls, properties etc. that are only visible to XAML after parsing the compiled assembly. @yatli thanks! This sounds similar to what our tooling does as well (no surprise...

> I'm not sure about the details :) But I guess it's somewhat hard-coded -- although it follows the convension (static member NamedProperty vs. property "Named"), the types are different...

@jtbrower thanks for your feedback. I've worked on this from the WinUI side of things and there's no offense taken, I'm sorry the work we've done hasn't been enough yet....