Closed Baka632 closed 1 year ago
Can you only reproduce this issue with VisualStateManager
? If so, can you try setting ReorderVSM to "None" and see if you can still reproduce the issue?
Yes, I can only reproduce this issue with VisualStateManager
And after setting ReorderVSM to "None", the issue disappeared.
Is leaving that setting as "None" feasible for your project? The challenge here is that the region could be around any arbitrary block of XAML.
Yes it is feasible for my project.
Usually VisualStateManager
is very long so I use region to keep my code tidy and I won't add other XAML element inside.
Thanks for confirming! Going to close this as wont fix for now as there is a viable workaround for handling VSM.
Describe the bug When XAML source code contains
<!--#endregion-->
, XamlStyle moves it wronglyBefore formatting:
After formatting:
To Reproduce Steps to reproduce the behavior:
<!--#endregion-->
Expected behavior
<!--#endregion-->
should follow the previous XAML elementScreenshots Before:
After:
External Configuration No
Version Info (please complete the following information):
Additional context No