问题描述
我是一名 .Net 开发人员，负责将经典的 asp 网站升级到 asp.net.该网站目前靠运气和泡泡糖运行，但没有足够的时间或金钱来阻止进展并进行全面重写.当然，我在升级时仍然需要能够提供新功能.
I am a .Net developer that has been tasked with upgrading a classic asp website to asp.net. The website is currently running on luck and bubble gum but there is not enough time or money to stop progress and do a full rewrite. Of course I will still need to be able to deliver new features while I am upgrading.
我应该使用什么策略来对asp.net进行平滑的渐变?我应该转换为单层 .net 解决方案，然后重构为适当的多层解决方案，还是应该现在设计我的业务和数据层?我应该直接升级到 3.5 还是直接升级到 1.1 并在之后升级到 2.0 或 3.5 更容易?
What strategies should I use to make a smooth gradual change to asp.net? Should I convert to a single tier .net solution and then refactor to a proper multi-tier solution or should I design my business and data layers now? Should I go straight to 3.5 or is it easier to just get to 1.1 and upgrade to 2.0 or 3.5 after?
完全转换可能需要 3-5 个月.还有一些现有的 1.1 代码，这就是我考虑将其作为起点的原因.
A full conversion would probably take 3-5 months. There is also some existing 1.1 code, which is why I am considering using that as a jumping off point.
推荐答案
长期以来，我一直是经典的 asp 程序员，现在是 ASP.NET 开发人员，我会花时间在 2.0 框架(如果你是 3.5想要/需要这些功能).
Having been a longtime classic asp programmer, and now an ASP.NET dev, I would take the time and architect it properly in the 2.0 framework (3.5 if you want/need the features).
我的上一份工作是我们正在重建大量非常糟糕的经典 asp 应用程序，nuke and pave"方法是最成功的.使用现有的经典应用作为您的功能规范和线框，并以此为基础构建您的任务和技术规范.
My last job we had a large handful of very badly build classic asp apps that we were rebuilding, and the "nuke and pave" approach was the most successful. Use the existing classic app as your functional spec and wireframes, and build your tasks and tech specs off of that.
这篇关于从 asp classic 转换为 asp.net 的最简单方法是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！