其中一个答案是x:name将在不同的程序语言中使用，如c#，而name将用于框架。说实话，我听起来就是这样。

Name can also be set using property element syntax with inner text, but that is uncommon. In contrast, x:Name cannot be set in XAML property element syntax, or in code using SetValue; it can only be set using attribute syntax on objects because it is a directive. If Name is available as a property on the class, Name and x:Name can be used interchangeably as attributes, but a parse exception will result if both are specified on the same element. If the XAML is markup compiled, the exception will occur on the markup compile, otherwise it occurs on load.

X:如果有自定义控件，Name可能会导致内存问题。它将为NameScope条目保留一个内存位置。

我建议除非迫不得已，否则不要使用x:Name。

它们都是一样的东西，很多框架元素本身公开了name属性，但对于那些不公开的元素，你可以使用x:name -我通常只使用x:name，因为它适用于任何东西。

控件可以将名称本身公开为依赖属性(因为它们需要在内部使用该依赖属性)，也可以选择不这样做。

更多细节在msdn这里和这里:

Some WPF framework-level applications might be able to avoid any use of the x:Name attribute, because the Name dependency property as specified within the WPF namespace for several of the important base classes such as FrameworkElement/FrameworkContentElement satisfies this same purpose. There are still some common XAML and framework scenarios where code access to an element with no Name property is necessary, most notably in certain animation and storyboard support classes. For instance, you should specify x:Name on timelines and transforms created in XAML, if you intend to reference them from code. If Name is available as a property on the class, Name and x:Name can be used interchangeably as attributes, but an error will result if both are specified on the same element.

我总是使用x:Name变量。 我不知道这是否会影响性能，我只是觉得它更容易，原因如下。 如果您有自己的用户控件驻留在另一个程序集中，只有“Name”属性并不总是足够的。这使得使用x:Name属性更加容易。

x:Name的意思是:在后面的代码中创建一个字段来保存对该对象的引用。

Name表示:设置该对象的Name属性。