将网站从 .NET 2.0 迁移到 .NET 3.5 的风险
网站从2.0框架升级到3.5框架有哪些固有风险？
我知道升级中提供给我的功能，只是好奇升级时是否可能出现任何已知问题。
IE Function X 过去以这种方式运行，现在以新的方式运行。
What are the inherent risk of upgrading a website from the 2.0 framework to the 3.5 framework?
I know the features given to me in the upgrade, just curious if there are any known issues that may pop up when upgrading.
I.E. Function X used to behave this way, and now behaves a new way.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
每当我这样做时，我都很少遇到问题。
3.5 实际上在 IIS 中作为 2.0 运行，所以实际上 3.5 的东西是额外的。
破解并编译，应该没问题。
I have had very few problems whenever I have done this.
3.5 actually runs as 2.0 in IIS so really the 3.5 things are extras.
Give it a crack and compile, should be fine.
据我所知，在将项目定位到 .NET 3.5 后，您只需检查一个问题：web.config 文件更改。 这里有一些关于这个主题的信息。
除此之外，.NET 在 2.0、3.0 和 3.5 版本之间进行了大量扩展。但库核心在考虑其功能行为方面相当稳定。
还有一点注意。我升级了 3 个不同的 Web 项目，没有任何问题，甚至没有触及 web.config。
AFAIK there's only one issue you should check after targeting your project to .NET 3.5: web.config file changes. There's some info on this subject here on SO.
Other than that .NET was heavily extended between 2.0, 3.0 and 3.5 versions. But library core is pretty stable in what considers its functionality behavior.
One more note. I upgraded 3 different web projects without any problem and not even touching web.config.
我遇到的唯一主要的 2.0->3.5 问题区域是在 Web.Config 中，并且集中在对 System.Web.Extensions 2.0 的引用上。如果您使用 Visual Studio 界面更改项目的 .NET 版本，VS 将自动修复 Web.config 文件中的大多数引用不兼容性。
至于代码差异，您可能会发现某些方法已被新版本废弃，但我从未遇到过任何彻底的破坏。
微软拥有非常严格的向后兼容性标准，以便尽可能减少重大升级的影响。
The only major 2.0->3.5 trouble areas I have encountered were in the Web.Config and centered around references to System.Web.Extensions 2.0. If you use the Visual Studio interface to change your project's .NET version, VS will automatically fix most reference incompatibilities in your Web.config file.
As for code differences, you're likely to find that some methods which have been obsoleted by newer versions, but I've never encountered any that outright break.
Microsoft holds a very strict backwards-compatibility standard so that they can reduce the impact of major upgrades as much as possible.