反对将开发中的 Silverlight 2 项目更新到 Silverlight 3 的问题或原因？
我目前正在开发一个最近开始的项目，目标日期为 2010 年，主要使用 Silverlight 2 开发，并使用 March Silverlight 2 工具包。
既然 Silverlight 3 已成为黄金，是否有任何理由不将项目迁移到 Silverlight 3，以便能够利用新增功能和改进的性能？ 鉴于 Silverlight 2 应用程序存在“怪异”模式，当项目仍处于早期开发阶段时，处理任何此类更新似乎会更容易。
我主要关心的两个领域是 Silverlight Toolkit（我可以简单地安装 Silverlight 3 版本的 Toolkit，还是 2 版本可以开箱即用）和主题。
主题化（使用工具包）一直是 Silverlight 2 中令人头疼的一个原因，我需要创建各种解决方法以确保动态内容具有正确的主题化，同时保持性能。 Silverlight 3 将主题作为内置功能进行宣传 - 这是 Toolkit 版本主题的集成，还是 Silverlight 引入了完全不同的主题机制？
I currently have a recently started project in development with a 2010 target date developed primarily in Silverlight 2, making use of the March Silverlight 2 Toolkit.
Now that Silverlight 3 is gold, is there any reason to not migrate the project to Silverlight 3 in order to be able to take advantage of added features and improved performance? Given the "quirks" mode present for Silverlight 2 applications, it would seem easier to handle any such an update while the project is still in early development.
My two main areas of concern are with the Silverlight Toolkit (can I simply install the Silverlight 3 version of the Toolkit, or does the 2 version work out of the box), and with theming.
Theming (using the Toolkit) has been a cause for headaches with Silverlight 2, and I've needed to create various work arounds to ensure dynamic content is properly themed while maintaining performance. Silverlight 3 advertises theming as a built in feature - is this an integration of the Toolkit's version of theming, or does Silverlight introduce a completely different theming mechanism?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我们刚刚完成了 SL3 RTM 的升级，进展顺利，我不得不推荐它。 请记住，控件已在您使用的工具包版本和 Silverlight 3 之间移动。一些控件从工具包转移到 SL3，而一些 SL3 beta（也许还有 SL2？）控件被推回工具包。 以下是 2 和 3 之间的更改列表：
http://docs.google.com/View? id=dnkk749_0czvc86gx
We just completed an upgrade to SL3 RTM, it went smoothly and I'd have to recommend it. Keep in mind that controls have moved between the toolkit release you're using and Silverlight 3. Some of the controls went from toolkit to SL3 and some SL3 beta (maybe SL2 also?) controls were pushed back into the toolkit. Here's the list of changes between 2 and 3:
http://docs.google.com/View?id=dnkk749_0czvc86gx
如果您的项目不会持续太久，您不妨现在切换到 3。 你遇到的任何头痛都不会那么严重，因为你的整个应用程序都不会完成。
尽早纠正错误并做出改变总是比稍后更容易。
If you're project is not due to out for that long, you might as well switch to 3 now. Any headaches you encounter won't be as serious because you're whole application won't be finished.
It's always easier to fix mistakes and make changes sooner rather than later.
安装 Silverlight 3 工具时 (http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9442b0f2-7465-417a-88f3-5e7b5409e9dd），查看 Silverlight 3 SDK 中的 Changes.docx。 它可以帮助您缓解升级问题并评估迁移可能需要的时间。
顺便说一句，Silverlight 3 RTM 已推出。 不升级的唯一原因是您可能需要花费的时间......
When you install Silverlight 3 tools (http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9442b0f2-7465-417a-88f3-5e7b5409e9dd), check out Changes.docx in the Silverlight 3 SDK. It can help you mitigating upgrade issues and assessing the time you may need for the migration.
BTW, Silverlight 3 RTM is out. The only reason not to upgrade would be the amount of time you may have to spend...