陷阱用于将.NET 2.0解决方案，以.NET 3.5 [英] Pitfalls for converting a .net 2.0 solution to .net 3.5

问题描述

我们正在与20多个项目，从.NET 2.0至3.5，并在同一时间从Visual Studio 2005迁移到2008年。我们也同时切换从MS Entlib 2.0至4.0的解决方案。

We're moving a solution with 20+ projects from .net 2.0 to 3.5 and at the same time moving from Visual Studio 2005 to 2008. We're also at the same time switching from MS Entlib 2.0 to 4.0.

• 有什么理由不让 Visual Studio的向导转换 我们的解决方案？
• 3.5完全向后兼容 2.0？
• 是Entlib 4.0完全向后兼容 2.0？

• Is there any reasons not to let the Visual Studio wizard convert the solution for us?
• Is 3.5 fully backwards compatible with 2.0?
• Is Entlib 4.0 fully backwards compatible with 2.0?

编辑：我可能是有点混乱，当我写这一点，向后兼容的解释是;有什么存在于一个2.0的项目，将无法正常工作/编译3.5

I might been a bit confused when I wrote this, the backwards compatability is supposed to mean; is there anything that exists in a 2.0 project that will not work/compile in 3.5

：）

//是W

推荐答案

我们提升一个相当大的溶液（20 +项目）2005〜2008年，但它是真的微不足道。项目升级只是基本。底层框架仍然是因为两个3.0 / 3.5和2.0共享相同的核心架构是相同的。

We upgrade a rather large solution (20+ projects) from 2005 to 2008 but it was really trivial. Project upgrade only basically. The underlying framework is still the same since both 3.0/3.5 and 2.0 share the same core framework.

正如上面有人说，即使你升级，你并不需要更改架构参考项目 - 事实上，它默认为离开该框架为2.0，而不是将其更改为3.0 / 3.5。这意味着您将无法充分利用3.0 / 3.5功能的优势，直到您更改引用（项目属性页面，申请表目标框架字段），但它也意味着你是更放心，不会有其他兼容性问题（你会得到一个错误增加3.0 / 3.5 code，直到参考值发生改变）。

As was said above, even though you are upgrading, you don't need to change the framework reference for the projects - in fact, it defaults to leaving the framework at 2.0 instead of changing it to 3.0/3.5. This means you will not be able to take advantage of 3.0/3.5 features until you change the reference (Project Properties page, Application Table "Target Framework" field) but it also means you are that much more assured there won't be additional compatibility issues (as you will get an error adding 3.0/3.5 code until that reference is changed).

TFS 2008的新特性不容忽视要么虽然你并不需要升级你的应用程序能够使用TFS 2008。

New features of TFS 2008 shouldn't be overlooked either though you don't need to upgrade your app to be able to use TFS 2008.

1.1到2.0的转换是更痛苦的...

1.1 to 2.0 conversion was much more painful...

这篇关于陷阱用于将.NET 2.0解决方案，以.NET 3.5的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！