将 .net 1.1 解决方案转换为 .net 2.0 的陷阱
In this question superwiren asks about the pitfalls for converting a .net 2.0 solution to .net 3.5.
What about .net 1.1 to .net 2.0?
Is 2.0 fully backwards compatible with 1.1?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我认为这取决于您的代码，最好的选择是执行试运行，看看它会生成什么错误。
我不认为 .NET 2.0 是完全向后兼容的，尽管他们声称是这样。
常见转换问题和解决方案
1.1 到 2.0 兼容性
I think its depends on your code, the best option is to perform a trial run and see what errors it will generate.
I dont think .NET 2.0 is fully backwards compatible, though they claim it is.
Common conversion issues and solutions
1.1 to 2.0 compatibility
我已经完成了几次 ASP.NET 1.1 到 2.0 的转换（中型网站），我们发现 Visual Studio 转换向导使事情变得非常简单。 我们没有遇到任何不兼容问题，我们真正改变的唯一事情就是用新函数替换已弃用的 api 调用。 我建议你试一试。
I've worked on a couple of ASP.NET 1.1 to 2.0 conversions (medium-sized websites), and we found that the Visual Studio conversion wizard made things pretty easy. We didn't run into any incompatibility issues, and the only things we really changed involved replacing deprecated api calls with new functions. I'd suggest you just give it a shot.
不它不是。 2.0 中出现了大量重大更改，但根据您的应用程序的编码方式，它可能根本不会受到影响。 以下文档包含从 1.1 到 2.0 的所有更改的链接...
重大更改假设
您没有使用 2.0 中引入的应用程序中的任何内容，那么向后兼容的机会就更大。
2.0 中的新增功能
No it is not. There were a numerous amount of breaking changes presented in 2.0, but depending on how your application was coded, it may not be affected at all. Here's a document with links to all the changes from 1.1 to 2.0...
Breaking Changes
Assuming you didn't use anything in the application that was introduced in 2.0, then there's a larger chance of backwards compatibility.
What's New in 2.0
我在代码中发现的唯一问题是 asp.net 中的两个控件使用不同的大小写调用相同的东西。 这曾经在 1.1 中工作，但在 2.0 中崩溃了。
无论如何，这是一个代码味道，所以没有理由为此哭泣
The only issue I've found in my code is having two controls in asp.net called the same thing with different casing. this used to work in 1.1, but crashes 2.0
It's a codesmell anyway, so there's no reason to cry about it