microsoft / microsoft/microsoft-ui-xaml
Renaming properties not propogating to XAML
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.4k
- Forks
- 942
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 105
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported reproduction: rename a C# property used by an XAML binding and observe whether the binding is unchanged or incorrectly prefixed. Investigate the renaming service and its failure banner; done means all affected bindings remain valid and the app builds successfully after the rename.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100