blocks|key|1402862|text|我总是使用x:Name变量。我不知道这是否会影响性能，我只是发现它更容易，原因如下。如果您自己的用户控件驻留在另一个程序集中，那么"Name“属性并不总是足够的。这使得只粘贴x:Name属性变得更容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1402863|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I always use the x:Name variant.
I have no idea if this affects any performance, I just find it easier for the following reason.
If you have your own usercontrols that reside in another assembly just the "Name" property won't always suffice. This makes it easier to just stick too the x:Name property.

blocks|key|1617584|text|它不是一个WPF项，而是一个标准的XML项，BtBh已经正确地回答了这个问题，x指的是默认名称空间。在XML中，如果没有为元素/属性加上名称空间前缀，它会假定您需要缺省名称空间。因此，对于x:Name来说，只输入Name只不过是一种速记。有关XML名称空间的更多详细信息，请参阅link+text|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1617585|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/6088/btbh|1|http://www.w3schools.com/XML/xml_namespaces.asp^0|2M|6|2Y|4|M|4|0|3V|9|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]|$9|X|A|Y|1|Z]]|E|$]]|$1|F|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|O]]]]

It's not a WPF item but a standard XML one and <a href="https://stackoverflow.com/users/6088/btbh">BtBh</a> has correctly answered it, x refers to the default namespace. In XML when you do not prefix an element/attribute with a namespace it assumes you want the default namespace.
So typing just <code>Name</code> is nothing more than a short hand for <code>x:Name</code>. More details on XML namespaces can be found at <a href="http://www.w3schools.com/XML/xml_namespaces.asp" rel="nofollow noreferrer">link text</a>

blocks|key|1402932|text|在XAML中只有一个名字，那就是x:Name。框架(如WPF+)可以有选择地将其属性之一映射到XAML的x:Name，方法是在类上使用RuntimeNamePropertyAttribute，该类将一个类属性指定为映射到XAML的x:Name属性。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1402933|这样做的原因是为了允许框架在运行时已经有了“名称”的概念，比如WPF。例如，在WPF中，FrameworkElement引入了Name属性。|1402934|通常，类不需要存储x:Name的名称即可使用。对于XAML，所有的x:Name手段都是生成一个字段来存储代码背后的类中的值。运行时对该映射执行的操作依赖于框架。|1402935|那么，为什么有两种方法可以做同样的事情呢？答案很简单，因为有两个概念映射到一个属性上。WPF希望在运行时保留元素的名称(可通过绑定等方式使用)，而XAML需要知道您希望哪些元素可由类后台代码中的字段访问。WPF通过将Name属性标记为x:Name的别名将这两者联系在一起。|1402936|将来，XAML将对x:Name有更多的用途，比如允许您通过按名称引用其他对象来设置属性，但在3.5及更早版本中，它仅用于创建字段。|1402937|你是否应该使用其中之一，实际上是一个风格问题，而不是一个技术问题。我将把这个问题留给其他人来推荐。|1402938|另请参阅AutomationProperties.Name+VS+x:Name，AutomationProperties.Name由辅助工具和一些测试工具使用。|1402939|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/4605777/automationproperties-name-vs-xname^0|G|6|1G|6|1V|S|0|18|G|0|9|6|X|6|0|0|0|0|4|Z|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1E|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1F|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1G|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1H|8|@]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|R|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]]]

There really is only one name in XAML, the <code>x:Name</code>. A framework, such as WPF, can optionally map one of its properties to XAML's <code>x:Name</code> by using the <code>RuntimeNamePropertyAttribute</code> on the class that designates one of the classes properties as mapping to the x:Name attribute of XAML.

The reason this was done was to allow for frameworks that already have a concept of "Name" at runtime, such as WPF. In WPF, for example, <code>FrameworkElement</code> introduces a Name property.

In general, a class does not need to store the name for <code>x:Name</code> to be useable. All <code>x:Name</code> means to XAML is generate a field to store the value in the code behind class. What the runtime does with that mapping is framework dependent.

So, why are there two ways to do the same thing? The simple answer is because there are two concepts mapped onto one property. WPF wants the name of an element preserved at runtime (which is usable through Bind, among other things) and XAML needs to know what elements you want to be accessible by fields in the code behind class. WPF ties these two together by marking the Name property as an alias of x:Name.

In the future, XAML will have more uses for x:Name, such as allowing you to set properties by referring to other objects by name, but in 3.5 and prior, it is only used to create fields.

Whether you should use one or the other is really a style question, not a technical one. I will leave that to others for a recommendation.

See also <a href="https://stackoverflow.com/questions/4605777/automationproperties-name-vs-xname">AutomationProperties.Name VS x:Name</a>, AutomationProperties.Name is used by accessibility tools and some testing tools.

blocks|key|1617722|text|它们不是一回事。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1617723|x:Name是一个xaml概念，主要用于引用元素。当您为元素赋予x:Name+xaml属性时，“指定的x:Name将成为处理xaml时在底层代码中创建的字段的名称，该字段包含对对象的引用。”(MSDN)因此，它是设计器生成的字段，默认情况下具有内部访问权限。|offset|length|style|CODE|1617724|Name是FrameworkElement的现有字符串属性，与任何其他wpf元素属性一样以xaml属性的形式列出。|1617725|因此，这也意味着x:Name可以在更广泛的对象上使用。这是一种允许xaml中的任何内容被给定名称引用的技术。|1617726|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/dotnet/framework/xaml-services/x-name-directive^0|0|0|6|1F|6|2O|4|0|0|0|4|5|G|0|8|6|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]|$D|X|E|Y|F|G]]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@$D|13|E|14|F|G]|$D|15|E|16|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

They are not the same thing.

<code>x:Name</code> is a xaml concept, used mainly to reference elements. When you give an element the x:Name xaml attribute, "the specified <code>x:Name</code> becomes the name of a field that is created in the underlying code when xaml is processed, and that field holds a reference to the object." (<a href="https://docs.microsoft.com/en-us/dotnet/framework/xaml-services/x-name-directive" rel="noreferrer">MSDN</a>) So, it's a designer-generated field, which has internal access by default.

<code>Name</code> is the existing string property of a <code>FrameworkElement</code>, listed as any other wpf element property in the form of a xaml attribute.

As a consequence, this also means <code>x:Name</code> can be used on a wider range of objects. This is a technique to enable anything in xaml to be referenced by a given name.

blocks|key|1617759|text|X:Name可能会导致内存问题，如果您有自定义控件。它将为NameScope条目保留一个内存位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1617760|我建议除非迫不得已，否则永远不要使用x:Name。|1617761|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

X:Name can cause memory issues if you have custom controls. It will keep a memory location for the NameScope entry. 

I say never use x:Name unless you have to.

blocks|key|1617845|text|唯一的区别是，如果你使用用户控件到来自同一程序集的控件中，那么Name将不能识别你的控件，并且你会得到一个错误“Use+x:Name+for+Controls+in+The+Same+Assembly”。So+x:Name是WPF中命名控件的WPF版本控制。Name仅用作Winform+Legacy。他们希望在WPF和winforms中区分控件的命名，因为他们使用Xaml中的属性来标识控件与其他程序集，他们使用x:作为控件的名称。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1617846|请记住，不要仅仅为了保留控件的名称而给它命名，因为它作为空白驻留在内存中，它会给你一个警告，说明名称已经应用于控件，但它从未使用过。|1617847|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The only difference is that if you are using user Controls into a control from Same Assembly then Name will not identify your control and you will get an error " Use x:Name for controls in the same Assembly". 
So x:Name is the WPF versioning of naming controls in WPF. Name is just used as a Winform Legacy. They wanted to differentiate the naming of controls in WPF and winforms as they use attributes in Xaml to identify controls from other assemblies they used x: for Names of control. 

Just keep in mind dont put a name for a control just for the sake of keeping it as it resides in memory as a blank and it will give you a warning that Name has been applied for a control buts its never used.

blocks|key|1617893|text|其中一个答案是x:name将在不同的编程语言中使用，例如c#，而name将用于框架。老实说，这就是我听起来的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1617894|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One of the answers is that x:name is to be used inside different program languages such as c# and name is to be used for the framework. Honestly that is what it sounds like to me.

blocks|key|1617973|text|x:Name的意思是:在后台代码中创建一个字段来保存对此对象的引用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1617974|Name表示:设置此对象的name属性。|1617975|entityMap^0|0|6|0|0|4|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

<code>x:Name</code> means: create a field in the code behind to hold a reference to this object.

<code>Name</code> means: set the name property of this object.

blocks|key|1618039|text|在XAML中声明Button元素时，您引用的是在windows运行时中定义的一个名为Button的类。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1618040|按钮有许多属性，如背景、文本、边距、.....以及一个名为Name的属性。|1618041|现在，当您在XAML中声明一个Button时，就像创建一个恰好有一个名为Name的属性的匿名对象。|1618042|一般而言，您不能引用匿名对象，但在WPF框架中，XAML处理器使您能够通过为Name属性指定的任何值来引用该对象。|1618043|到目前一切尚好。|1618044|创建对象的另一种方法是创建命名对象而不是匿名对象。在本例中，XAML名称空间有一个名为Name的对象的属性(由于它在XAML名称空间中，因此可以使用X:)，您可以设置该属性，以便标识对象并引用它。|1618045|结论：|1618046|Name是一个特定对象的属性，但X:Name是该对象的一个属性(有一个定义通用对象的类)。|1618047|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

When you declare a Button element in XAML you are referring to a class defined in windows run time called Button.

Button has many attribute such as background, text, margin, ..... and an attribute called Name.

Now when you declare a Button in XAML is like creating an anonymous object that happened to have an attribute called Name.

In general you can not refer to an anonymous object, but in WPF framework XAML processor enables you to refer to that object by whatever value you have given to Name attribute.

So far so good.

Another way to create an object is create a named object instead of anonymous object. In this case XAML namespace has an attribute for an object called Name (and since it is in XAML name space thus have X:) that you may set so you can identify your object and refer to it.

Conclusion:

Name is an attribute of a specific object, but X:Name is one attribute of that object (there is a class that defines a general object).

Sometimes it seems that the <code>Name</code> and <code>x:Name</code> attributes are interchangeable.
So, what are the definitive differences between them, and when is it preferable to use one over the other?
Are there any performance or memory implications to using them the wrong way?

In WPF, what are the differences between the x:Name and Name attributes?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有时，Name和x:Name属性似乎是可以互换的。那么，它们之间的明确区别是什么，什么时候使用一种比另一种更可取？以错误的方式使用它们是否会对性能或内存产生影响？

问在WPF中，x:Name和Name属性有什么不同？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在WPF中，x:Name和Name属性有什么不同？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在WPF中，x:Name和Name属性有什么不同？
EN