This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 31%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVG%3C/text%3E%3C/svg%3E)
We are in the process of moving in-app strings to resource files for our Winui3 application. In this, we are now using x:uid for the XAML controls.
We would like to know whether we can use Resource Manager to get the resource for each property of the XAML controls
X:Uid Approach:
Resource Binding Approach:
Code behind:
Will this have any effect on the performance? or Is x:uid approach preferred for Winui3 applications
Hello,
Welcome to Microsoft Q&A!
As far as I'm concerned, both methods are fine, and you could choose whichever method you want in winui3.
In my opinion, the x:Uid method is relatively simpler.
Thank you.
Jeanine
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hii @Jeanine Zhang-MSFT ,
Thank you for your response.
In our app, we have many strings(For example: Save, Cancel, Select) that are repeatedly used for Xaml control properties like Content, Label, Placeholder, etc. We would like to prefer the Binding approach so that we can avoid having multiple entries for the same string in the resource files or is there any other way we can tackle this in the X:Uid method
As far as I'm concerned, there is no way we can tackle this in the X:Uid method.
x:Uid values are unique within an XML-encoded file that represents XAML.
UWP XAML has somewhat different rules for x:Uid uniqueness than previous XAML-utilizing technologies used. For UWP XAML it is legal for the same x:Uid ID value to exist as a directive on multiple XAML elements. However, each such element must then share the same resolution logic when resolving the resources in a resource file. Also, all XAML files in a project share a single resource scope for purposes of x:Uid resolution, there is no concept of x:Uid scopes being aligned to individual XAML files.
If you have a lot of duplicate resource values, I suggest you could use Binding approach.