Morten Nielsen

> we weren't able to justify spending our smaller resources on migrating the WPF MarkupCompiler to use System.Xaml. Perhaps if we can get some guidelines how to do that, the...

Is the v1.7experimental release the final TitleBar API? I'm a little confused that it is identical to the 1.6 one, and from my understanding it was pulled from the 1.6...

@michael-hawker awesome! Great to hear!

> Would folks have preferred LeftHeader/Content/RightHeader instead to align with more established patterns? My main concern here is I don't understand how this should work in an RTL scenario. 1....

@michael-hawker ugh that's tough but I can understand the issues you're dealing with here, and the reasoning for making this change. Thank you for the above description. I do wish...

@jozefizso Correct. The `AppWindow` API is not really a WinUI3 API - It's a generic Windows API (which is why I was rather disappointed seeing a recent release exposing `AppWindow`...

Make sure you account for dpi ```cs var scale = (this.Content as FrameworkElement).XamlRoot.RasterizationScale; this.AppWindow.Resize(new((int)width*scale, (int)height*scale)) ``` This is one reason that IMHO the AppWindow APIs really shouldn’t have been a...

@kasperisage you should use the scale off XamlRoot

@Jay-o-Way It's a feature missing from the control, but if you subclass it you can now do this: https://github.com/Esri/arcgis-maps-sdk-dotnet-demos/blob/b80e13f37d2835d38444ac21dde7580d5024163c/src/MapViewer/ArcGISMapViewer.Controls/ScaleRangeSelector.cs#L51-L57

Yeah being able to write ```xml ``` would have been way more intuitive, but unfortunately [the baseclass of Window is wrong](https://github.com/microsoft/microsoft-ui-xaml/issues/7305) and prevents this.