Is the June 2009 WPF Toolkit safe to use in applications that will be shipped out to customers?
2009年6月的WPF工具包是否可以安全地用于将要发送给客户的应用程序?
I'm seriously concerned that my application will crash three days prior to release. This concern stems from the fact that that the WPF Toolkit does not seem to be endorsed by Microsoft, even though it appears to be developed by established developers on Microsoft's WPF team.
我非常担心我的申请会在发布前三天崩溃。这种担忧源于这样一个事实,即WPF工具包似乎并未得到微软的认可,即使它似乎是由微软WPF团队的老牌开发人员开发的。
I'd like to think that I can trust these official WPF developers to make sure their stuff won't cause any catastrophic problems for me down the road - but I need reassurance. I can't afford any problems in the next few weeks.
我想我可以相信这些正式的WPF开发人员确保他们的东西不会给我带来任何灾难性的问题 - 但我需要保证。在接下来的几周里我无法承受任何问题。
Pleas, give me your opinions on this subject.
请求,就这个问题给我你的意见。
Some links:
MSDN search results for "WPF Toolkit"
“WPF工具包”的MSDN搜索结果
WPF Toolkit: DataGrid Feature Walkthrough
The DataGrid control is the only part of the WPF Toolkit that I am currently interested in using.
WPF工具包:DataGrid功能演练DataGrid控件是我目前有兴趣使用的WPF工具包的唯一部分。
WPF Toolkit - June 2009 Release - Binaries and Source Code Flies
These files are hosted at Codeplex. I found this link in a few different MSDN articles, and it seems to be the most common link provided to people asking for these resources.
WPF工具包 - 2009年6月发行 - 二进制文件和源代码过滤这些文件托管在Codeplex。我在一些不同的MSDN文章中找到了这个链接,它似乎是提供给这些资源的人们最常见的链接。
2 个解决方案
#1
Read here. The current release is marked as Stable (and not yet Matured).
在这里阅读当前版本标记为稳定(尚未成熟)。
From the release notes: "Also new in the June release, we are introducing the concept of Quality Bands to rate the quality of the controls and features in the release."
从发布说明:“在6月发布的新版本中,我们引入了质量带的概念来评估版本中控件和功能的质量。”
"Stable
Stable components are suitable for the vast majority of usage scenarios and will have incorporated most major design and functionality feedback. They are designed to address over 90% of customer scenarios and will continue evolving via limited bug fixes and fit-and-finish work. Stable is similar to "Beta" in other projects. Stable components will have a very small number of breaking API or behavior changes when feedback demands it."
稳定的组件适用于绝大多数使用场景,并且将包含大多数主要的设计和功能反馈。它们旨在解决超过90%的客户场景,并将通过有限的错误修复和完成工作继续发展。稳定与其他项目中的“Beta”类似。当反馈需要时,稳定的组件将具有非常少量的破坏API或行为变化。“
I don't know if it is the case with this toolkit, but Microsoft does use codeplex for out of band releases of things that didn't make it to the .net framework or that will be part of future versions of the framework.
我不知道这个工具包是否属于这种情况,但是微软确实将codeplex用于带外版本的事情,这些版本没有进入.net框架,或者将成为未来版本框架的一部分。
#2
I do know from experience that the DataGrid release on Codeplex has the same interface and functionality as the one that will ship as part of PresentationFramework in .NET 4.0
我从经验中知道,Codeplex上的DataGrid版本具有与.NET 4.0中PresentationFramework的一部分相同的接口和功能。
Out product uses the WPF data grid and we are currently building on .NET 4.0 . At the beginning of our development cycle we used the WPF Toolkit from Codeplex, as the CTP version of WPF 4.0 did not include the full functionality. As of Beta 1 we have switched over to the framework version of the data grid and all we had to do was change our the declaration of the data grid object to use the framework version.
Out产品使用WPF数据网格,我们目前正在.NET 4.0上构建。在我们的开发周期开始时,我们使用了Codeplex的WPF Toolkit,因为WPF 4.0的CTP版本不包含完整功能。从Beta 1开始,我们已经切换到数据网格的框架版本,我们所要做的就是更改数据网格对象的声明以使用框架版本。
#1
Read here. The current release is marked as Stable (and not yet Matured).
在这里阅读当前版本标记为稳定(尚未成熟)。
From the release notes: "Also new in the June release, we are introducing the concept of Quality Bands to rate the quality of the controls and features in the release."
从发布说明:“在6月发布的新版本中,我们引入了质量带的概念来评估版本中控件和功能的质量。”
"Stable
Stable components are suitable for the vast majority of usage scenarios and will have incorporated most major design and functionality feedback. They are designed to address over 90% of customer scenarios and will continue evolving via limited bug fixes and fit-and-finish work. Stable is similar to "Beta" in other projects. Stable components will have a very small number of breaking API or behavior changes when feedback demands it."
稳定的组件适用于绝大多数使用场景,并且将包含大多数主要的设计和功能反馈。它们旨在解决超过90%的客户场景,并将通过有限的错误修复和完成工作继续发展。稳定与其他项目中的“Beta”类似。当反馈需要时,稳定的组件将具有非常少量的破坏API或行为变化。“
I don't know if it is the case with this toolkit, but Microsoft does use codeplex for out of band releases of things that didn't make it to the .net framework or that will be part of future versions of the framework.
我不知道这个工具包是否属于这种情况,但是微软确实将codeplex用于带外版本的事情,这些版本没有进入.net框架,或者将成为未来版本框架的一部分。
#2
I do know from experience that the DataGrid release on Codeplex has the same interface and functionality as the one that will ship as part of PresentationFramework in .NET 4.0
我从经验中知道,Codeplex上的DataGrid版本具有与.NET 4.0中PresentationFramework的一部分相同的接口和功能。
Out product uses the WPF data grid and we are currently building on .NET 4.0 . At the beginning of our development cycle we used the WPF Toolkit from Codeplex, as the CTP version of WPF 4.0 did not include the full functionality. As of Beta 1 we have switched over to the framework version of the data grid and all we had to do was change our the declaration of the data grid object to use the framework version.
Out产品使用WPF数据网格,我们目前正在.NET 4.0上构建。在我们的开发周期开始时,我们使用了Codeplex的WPF Toolkit,因为WPF 4.0的CTP版本不包含完整功能。从Beta 1开始,我们已经切换到数据网格的框架版本,我们所要做的就是更改数据网格对象的声明以使用框架版本。