Stone_Red/docs-desktop
1
0
Fork 0
mirror of https://github.com/Stone-Red-Code/docs-desktop.git synced 2026-09-09 23:43:28 +02:00
Code Issues Packages Projects Releases Wiki Activity

Links: .NET Desktop - Pass 2 (#111)

Browse Source
This commit is contained in:
David Coulter
2020-11-05 14:05:06 -08:00
committed by GitHub
parent 674b773578
commit 67f63a5a43
12 changed files with 35 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dotnet-desktop-guide/xaml-services/xuid-directive.md
+1 -1
View File
@@ -26,7 +26,7 @@ Provides a unique identifier for markup elements. In many scenarios, this unique
## Remarks
In [MS-XAML], `x:Uid` is defined as a directive. For more information, see [\[MS-XAML\] Section 5.3.6](https://docs.microsoft.com/previous-versions/msp-n-p/ff650760(v=pandp.10)).
In [MS-XAML], `x:Uid` is defined as a directive. For more information, see [\[MS-XAML\] Section 5.3.6](/previous-versions/msp-n-p/ff650760(v=pandp.10)).
`x:Uid` is discrete from `x:Name` both because of the stated XAML localization scenario and so that identifiers that are used for localization have no dependencies on the programming model implications of `x:Name`. Also, `x:Name` is governed by the XAML namescope; however, `x:Uid` is not governed by any XAML language defined concept of uniqueness enforcement. XAML processors in a broad sense (processors that are not part of the localization process) are not expected to enforce uniqueness of `x:Uid` values. That responsibility is conceptually on the originator of the values. The expectation of uniqueness of `x:Uid` values within a single XAML source is reasonable for consumers of the values, such as dedicated globalization processes or tools. The typical uniqueness model is that `x:Uid` values are unique within an XML-encoded file that represents XAML.