Renaming properties not propogating to XAML

[HEIC-to-JPEG-Dev]

Describe the bug

When renaming c# properties, in a viewmodel or in the .cs file of a page; the XAML bindings are not updated correctly. Sometimes not at all, and sometime the rename is prefixed to the property name in the binding

Why is this important?

Renaming should rename all instances, not some. It means compilation failures and, due to no background compilation of xaml, means the issues are only detected on rebuild or app run (compilaiton fails)

Steps to reproduce the bug

Rename a property that xaml x:binds to

Actual behavior

XAML properties are not renamed or wrongly renamed

Expected behavior

Renaming should not cause app compilation failures

Screenshots

No response

NuGet package version

WinUI 3 - Windows App SDK 1.8.3: 1.8.251106002

Windows version

Windows 11 (24H2): Build 26100

Additional context

The renaming service is tempromental at best, it often fails and a banner shows up in VS saying the service failed.

[ayushjai19]

@HEIC-to-JPEG-Dev Thanks for reporting this, but this issue seems to be in visual studio, so please report this to VS via report feedback in VS.

[HEIC-to-JPEG-Dev]

Yes it is a VS issue, but it is your (WinUI team) responsibility to make sure the tooling to make WinUI work, works. I’ve raised issues before and been passed from team to team and no-one would take responsibility. For example, WinUI team released a new “new project” template for VS, but the VS didn’t implement it. WinUI team blame VS, VS team blamed WinUI, and it took 4 months to get sorted. This is an ecosystem that needs to work; you can make the best framework ever, but if VS or csWinRT, or WASDK don’t work or are out of step, WinUI will never succeed and you will get the kind of negative feedback you get currently.

So, yes it’s a VS issue, but your responsibility to coordinate