问题描述
.NET框架似乎已经将DependencyProperty对象的两个实现
The .NET Framework seems to have two implementations of the DependencyProperty object
- System.Windows.DependencyProperty
- System.Workflow.ComponentModel.DependencyProperty
- System.Windows.DependencyProperty
- System.Workflow.ComponentModel.DependencyProperty
据我所知，在正常使用的第一个是在WPF和正常使用的，第二个是在WF但什么是如果有的话？
它们之间的差异如果我没有使用WPF / WF，仍然想使用的DependencyProperty这将是最好用？
任何计划合并到一个在未来？
I understand that the normal use of the first one is in WPF and the normal use of the second one is in WF but what are the differences between them if any?
If I was not using WPF/WF and still wanted to use a DependencyProperty which would be best to use?
Any plans to merge to one in the future?
推荐答案
的区别是微妙的，但它是相当清楚不过了：
The difference is subtle but it's quite clear enough:
System.Windows.DependencyProperty主要作为处理任何WPF依赖对象的依赖属性，并且可以提供有关财产的元数据可选的附加信息，如措施，动画，和许多WPF具体注册。
System.Windows.DependencyProperty is focused toward handling dependency property of any WPF dependency object, and you can register it with optional additional information about the metadata of the property, such as measures, animatable, and many WPF specific.
为什么？由于这种依赖属性就可以使用PropertyMetadata的派生类中进一步明确。这包括WPF的UIPropertyMetadata和FrameworkPropertyMetadata为WPF依赖属性的高级注册。
WHy? Because this dependency property can then be further specified using derived classes of PropertyMetadata. This includes WPF's UIPropertyMetadata and FrameworkPropertyMetadata for advanced registration of WPF dependency property.
System.Workflow.ComponentModel.DependencyProperty只能注册为一个简单的依赖属性，而不需要特定的WF的PropertyMetadata更多的信息。
System.Workflow.ComponentModel.DependencyProperty can only register as a simple dependency property, without needing additional information of specific WF's PropertyMetadata.
在present，有没有计划整合他们，因为他们两个在概念和内容不同。
At present, there's no plan to integrate them, since both of them are conceptually and contextually different.
这篇关于System.Windows.DependencyProperty与System.Workflow.ComponentModel.DependencyProperty的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！