Morten Nielsen

> There is a lot of code in production that uses System.Xaml separetely from WPF on server-side for purposes that aren't related to UI in any way, shape or form....

@AndrewKeepCoding That's a really nice find! That at least gives an (ugly) workaround for one of the issues and a little bit to go on, but still a lot of...

Here's a MUCH simpler reproducer: [ChatApp.zip](https://github.com/user-attachments/files/20303515/ChatApp.zip) Run the app and see a bunch of empty little gray and blue bubbles:  Next (while app is running) open `Themes\generic.xaml and in...

@Hemantxk Interesting workaround. Unfortunately that won't really work for 3rd party custom control libraries. The `Themes\Generic.xaml` file has always been implicitly included and this requirement would be a breaking change,...

@Hemantxk Here's the issue: Historically, when building custom control libraries, you _never_ had to explicitly include the themes\generic.xaml resources. It automatically includes and applies those styles. So a library that...

Here's an updated sample that adds a title to the ChatView control. [ChatApp2.zip](https://github.com/user-attachments/files/20784966/ChatApp2.zip) You can see that the title is using x:bind as well and works just fine:  However...

> FYI unchecking "Strip native debugging symbols" in the Project Properties accomplishes the same thing Yup that's the same as setting `MtouchNoSymbolStrip` (but the designer always does it bad with...

Just posting the comments from Discord triage here (thanks @rolfbjarne): Crash report using locally built strip (click to expand) ``` ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: strip [86963]...

With the latest RC2.1 workload update that shipped yesterday, it appears that Xcode 15 is now required, so we no longer can work around this issue. This makes it a...

@rolfbjarne That does appear to workaround it as well. What does this do?