不从 .Net 2.0 迁移到 .Net 3.5 有多晚？
我们很久以前就在 .Net 2.0 中开发了一些应用程序。我建议我的团队将基础从 .net 2.0 迁移到 .net 3.5sp1，并将重点和杠杆从 C# 3.0 转移，但我在这样做时遇到了困难。不迁移到 .net 3.5 和 C# 3.0 会有什么影响？您在这方面的经验是什么？您使用什么策略成功地将您的团队和项目迁移到.net3.5。
We have some applications that are being worked upon in .Net 2.0 since long back. I'm recommending my team to move the base from .net 2.0 to .net 3.5sp1 and focus and leverage from C# 3.0 but I'm facing difficulties in doing so. What are the implications of not migrating to .net 3.5 and C# 3.0 ? What are your experiences on this front and what tactics did you use to successfully migrate your team and projects to .net3.5.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
除了错过一些改进的框架添加（如 LINQ to SQL、LINQ to Objects、WCF、WPF 等）之外，留在 .NET 2.0 领域确实没有太多影响...
加上一些有趣的语法功能，如匿名方法， lambda 表达式和扩展方法。
迁移到 .NET 3.5 非常简单。向 MSFT 团队致敬。他们让这个过程变得非常轻松。
There really isn't too much implications with staying in .NET 2.0 land, other than missing out on some improved framework additions liek LINQ to SQL, LINQ to Objects, WCF, WPF etc...
Plus some fun syntax features like anonymous methods, lambda expressions, and extension methods.
Moving to .NET 3.5 is really straight forward. Hats off to the team at MSFT. They made the process very painless.
我会进行两步迁移。首先，我会迁移到 C# 3.0，同时坚持使用 .NET 2.0。您可以获得 C# 3.0 的大部分优势（包括通过 LINQBridge 获得 LINQ to Objects）。一旦开发人员将他们的思维方式转向 LINQ 和 lambda 表达式，爱上了扩展方法，使用自动属性美化了他们的代码，并迷上了 C# 3.0 的其余功能，我就会将应用程序迁移到 .NET Frameworks 3.5 SP1（这应该是毫不费力的，就像其他人提到的那样）。
I'd do a two-step migration. First I'd migrate to C# 3.0, while sticking with .NET 2.0. You get most of the benefits of C# 3.0 (including LINQ to Objects via LINQBridge). Once the developers have shifted their mindset to that of LINQ and lambda expressions, fallen in love with extension methods, beautified their code with automatic properties and got hooked on the rest of C# 3.0 features, I'd migrate the application to the .NET Frameworks 3.5 SP1 (which should be effortless, like others have mentioned).