将 ASP.NET 从版本 1.1 升级到 2.0 - 有任何问题吗？
我知道我们确实落后于时代，但我们即将从 .NET 1.1 升级到 .NET 2.0。
谢谢你的同情。
无论如何，有什么我们应该注意的问题吗？
在我们开始之前，您有什么一般性建议吗？
请不要发帖告诉我直接升级到 3.5：我们只允许使用 2.0！
我们主要使用 C#。
I know we are really behind the times here, but we are just about to upgrade from .NET 1.1 to .NET 2.0.
Thank you for your sympathy.
Anyhow, are there any gotchas we should look out for?
Do you have any general advice before we jump in?
Please do not post telling me to go straight to 3.5: 2.0 is all we're allowed!
We're using mostly C#.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
一个问题是 .NET 2.0 内容（在 1.1 中缺失）的本土 1.1 实现，例如RegistryHandler 等。 有时，您新移植的 2.0 代码看起来像是正确使用了 2.0 类，而实际上它实际上使用的是自行开发的版本。
One gotcha is home-grown 1.1 implementations of .NET 2.0 stuff (that was missing in 1.1) like RegistryHandler and so forth. Sometimes your newly-ported 2.0 code will look like it's properly using a 2.0 class when it's really using the home-grown version.
如果您要升级已经部署的应用程序，那么部署是另一个问题。 您必须将 IIS 中的 .NET 版本从 1.1 切换到 2.0。
Deployment is another gotcha, if you're upgrading an already-deployed app. You have to switch the .NET version in IIS from 1.1 to 2.0.
我记得我们必须更改一些客户端脚本，因为服务器控件生成 ClientID 的方式从 ASP.NET 1.1 更改为 2.0。
我不记得具体情况了，但是一些以前前缀为
ctl0_的 ID 变成了ctl00_...I remember we had to change some client scripts, because the way ClientIDs are generated for server controls changed from ASP.NET 1.1 to 2.0.
I don't remember the exact circumstances, but some IDs which previously wer prefixed
ctl0_becamectl00_...是的。 您需要了解的最重要的事情是使用 Web 应用程序项目，而不是网站。 网站使用完全不同的编译模型，迁移几乎是一场灾难。 Web 应用程序项目与 1.1 中的工作方式更加相似。
我们还遇到了从登录屏幕重定向的间歇性问题，但根据 Google 的说法，我们基本上是唯一遇到该问题的人 - 我们已经解决了它。
我们遇到的大多数其他问题都很小且易于解决，总体体验得到了净改善。
Yes. The most important thing for you to know is to use a Web Application Project, not a Web Site. Web Sites use a totally different compilation model and migration is pretty much a disaster. Web Application Projects are much more similar to how things worked in 1.1.
We also had an intermittent problem with redirecting from the login screen, but according to Google, we were basically the only ones who had that problem - we've since resolved it.
Most of the other problems we ran into were small and easy to navigate, and the overall experience was a net improvement.
以下是我在升级之前的建议：
Here is my recommendation before upgrading: