网站从 ASP .NET 2.0 升级到 3.5
我们有一个使用 Visual Studio 2005 开发和构建的 .NET 2.0 在 IIS 上运行的 Web 应用程序。
我们将升级到 .NET 3.5 并开始使用 Visual Studio 2008。以下是我的问题：
- 我注意到运行时仍然是 2.0 -基于。
当我在 Visual Studio 2008 中加载解决方案时，系统要求我进行转换，我照做了。然后我检查了默认项目的目标框架，它被设置为 3.5。然而，其他项目的所有其他目标框架都设置为 2.0。
我是否需要为解决方案中的每个项目手动设置目标框架从 2.0 到 3.5？
- 任何人都可以想到与网络应用程序转换有关的“陷阱”吗？
据我了解，由于大量的运行时和网页设计变化，1.1 到 2.0 的迁移是一个更加困难的问题。然而，2.0 到 3.5 并没有那么大的变化。
我目前的工作并不参与该升级，但我知道某些使用已弃用属性的文本区域标记存在问题，该属性在升级后无法正常运行。
有人能想到我可能遇到的类似问题吗？
- 在自己完成这样的转换之后，还有其他问题或想法吗？
谢谢，我很欣赏您的意见。
- -担 - -
We have a web application that runs on IIS using .NET 2.0 developed and built with Visual Studio 2005.
We're going to upgrade to .NET 3.5 and begin using Visual Studio 2008. Here are my questions:
- I note the runtime is still 2.0-based.
When I loaded the solution in Visual Studio 2008, I was asked to convert, and I did. I then checked the target framework for the default project, and it was set to 3.5. However, all of the other target frameworks for the other projects are set to 2.0.
Do I need to manually set the target frameworks from 2.0 to 3.5 for each of the projects in the solution?
- Are there any "gotcha's" anyone can think of to be concerned with a web-application conversion?
As I understand it, the 1.1 to 2.0 migration was a much more difficult issue due to the massive runtime and web-page design changes. However, 2.0 to 3.5 isn't such a big change.
I was not at my current job for that upgrade, but I understand there was a problem with some textarea tags using a deprecated attribute that failed to function correctly after the upgrade.
Can anyone think of any similar issues I might encounter?
- Any other issues or thoughts anyone has after having done such a conversion themselves?
Thanks, I appreciate the input.
---Dan---
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
没有必要，但我建议您这样做。 Visual Studio 实际上会根据目标框架版本过滤您可以引用的程序集。
我不知道从 2.0 迁移到 3.5 时的情况。您甚至不需要修改主机应用程序池的 CLR 版本。当您需要迁移到 4.0 时，可能会出现更多问题。
Not necessary, but I would recommend you to do so. Visual Studio actually filters the assemblies you can reference based on the target framework version.
Not any that I am aware of when migrating from 2.0 to 3.5. You don't even need to modify the CLR version of the host application pool. When you need to migrate to 4.0 there might be more issues.
如果您还要升级自己的目标服务器，根据我自己的经验，请对安装程序保持耐心。
它做了很多事情，包括卸载现有的 .NET 2.0 和 3.0 框架并进行大量替换。
安装程序看起来好像被卡住了。在我们的一台生产服务器上，它运行了近 20 分钟。我几乎准备好拔掉插头，然后它就神奇地复活了。
If you're also upgrading your own target server, from my own experiences, be patient with the installer.
It does quite a lot including uninstalling the existing .NET 2.0 and 3.0 frameworks and replacing it pretty much wholesale.
It can look as if the installer is stuck. On one of our production servers it ran for nearly 20 minutes. I was almost ready to pull the plug then it magically jumped into life.