移植=重写。几乎完全重写，除非您的 ASP 站点有一些您编写的 COM 组件，您可以重新利用这些组件并从 .NET 调用它们。由于它是重写，因此没有最简单的方法，无论您发现更容易使用什么。
Rewrite it.
Really it depends on what you want to do here. Do you want to add a new stand alone feature? That's sort of easy, just put the new app in a virtual directory. Do you want to share authentication? That's way more complicated. Do you want to share session? Forget it, it's not worth the pain.
Porting = rewrite. Pretty much a complete rewrite, unless your ASP site has some COM components you wrote which you could repurpose and call from .NET. As it's a rewrite there's no easiest for this, whatever you find easier to use.
在 ASP.NET 早期，我曾尝试将经典 ASP Web 应用程序迁移到 ASP.NET 站点。它生成的只是另一个在 .NET Framework 沙箱上运行的 ASP 站点，迟早会成为垃圾。
ASP.NET 与 ASP 是完全不同的范例，尽管名称保持不变。 ASP 完全依赖于内联代码，您可以在 ASP 文件中创建所有业务逻辑（或多或少）。 ASP.NET 在其总生命周期的不同级别上有自己的执行级别。尽管 ASP.NET MVC 与 ASP.NET Webforms 没有相似之处。
我的建议是重写您的应用程序以获得更好的可维护性和可管理性。您可以在设计阶段考虑 ASP.NET MVC，以便更好地考虑分离。
I have tried to migrate Classic ASP web applications to ASP.NET sites at the early age of ASP.NET. What it got produced is just another ASP site running on .NET Framework sandbox and it turned out to be a garbage sooner or later.
ASP.NET is completely a different paradigm than ASP, although the name stayed same. ASP is completely depends upon inline codes where you make all your business logic in your ASP files (more or less). ASP.NET has its own level of execution at a different level of its total life cycle. Even though ASP.NET MVC has no similarity with ASP.NET Webforms.
My suggestion would be to rewrite your application for better maintainability and manageability. You may consider ASP.NET MVC on your design phase for better concern of separation.
发布评论
评论（2）
重写它。
实际上，这取决于您想在这里做什么。您想添加新的独立功能吗？这很简单，只需将新应用程序放在虚拟目录中即可。您想分享身份验证吗？那要复杂得多。您想分享会话吗？算了，痛苦不值得。
移植=重写。几乎完全重写，除非您的 ASP 站点有一些您编写的 COM 组件，您可以重新利用这些组件并从 .NET 调用它们。由于它是重写，因此没有最简单的方法，无论您发现更容易使用什么。
Rewrite it.
Really it depends on what you want to do here. Do you want to add a new stand alone feature? That's sort of easy, just put the new app in a virtual directory. Do you want to share authentication? That's way more complicated. Do you want to share session? Forget it, it's not worth the pain.
Porting = rewrite. Pretty much a complete rewrite, unless your ASP site has some COM components you wrote which you could repurpose and call from .NET. As it's a rewrite there's no easiest for this, whatever you find easier to use.
在 ASP.NET 早期，我曾尝试将
经典 ASPWeb 应用程序迁移到ASP.NET站点。它生成的只是另一个在 .NET Framework 沙箱上运行的 ASP 站点，迟早会成为垃圾。ASP.NET 与 ASP 是完全不同的范例，尽管名称保持不变。 ASP 完全依赖于内联代码，您可以在 ASP 文件中创建所有业务逻辑（或多或少）。 ASP.NET 在其总生命周期的不同级别上有自己的执行级别。尽管 ASP.NET MVC 与 ASP.NET Webforms 没有相似之处。
我的建议是重写您的应用程序以获得更好的可维护性和可管理性。您可以在设计阶段考虑 ASP.NET MVC，以便更好地考虑分离。
I have tried to migrate
Classic ASPweb applications toASP.NETsites at the early age of ASP.NET. What it got produced is just anotherASPsite running on.NET Frameworksandbox and it turned out to be a garbage sooner or later.ASP.NET is completely a different paradigm than ASP, although the name stayed same. ASP is completely depends upon inline codes where you make all your business logic in your ASP files (more or less). ASP.NET has its own level of execution at a different level of its total life cycle. Even though ASP.NET MVC has no similarity with ASP.NET Webforms.
My suggestion would be to rewrite your application for better maintainability and manageability. You may consider ASP.NET MVC on your design phase for better concern of separation.