什么是从ASP经典转换为ASP.NET的最简单的方法？ [英] What is the easiest way to convert from asp classic to asp.net?

问题描述

我是一直负责升级传统的ASP网站asp.net .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 code，这就是为什么我使用的考虑，作为一个跳点。

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应用程序，而核弹和铺路的做法是最成功的。使用现有的经典应用为你的功能规格，线框图，并建立您的任务和技术规格掉了。

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经典转换为ASP.NET的最简单的方法？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！