简体   繁体   English

在Windows Server 2003 IIS中将ASP.NET页面与ASP页面混合

[英]Mixing ASP.NET pages with ASP Pages in windows server 2003 IIS

I've got a lot of Classic ASP pages in production on a Windows Server 2003 64-bit machine. 我在Windows Server 2003 64位计算机上生产了很多Classic ASP页面。 I've also got .NET on there working. 我也有.NET在那工作。

I'm starting to move the ASP ajax pages (pages that receive ajax calls from the Classic ASP) to ASP.NET/C# to take advantage of the business/data/logging layer I've got set up there in C#. 我开始将ASP Ajax页面(从Classic ASP接收Ajax调用的页面)移动到ASP.NET/C#,以利用我在C#中设置的业务/数据/日志记录层的优势。

I've figured on securing the ASPX pages by way of a "token" that I create in the database in ASP and then pass to the ASPX page, which then uses it to validate that it's a legit call and destroys it. 我已经想到了通过在ASP中的数据库中创建的“令牌”来保护ASPX页面,然后将其传递给ASPX页面,然后使用它来验证它是合法调用并销毁它。

My big question is - aside from making the ASPX pages, do I need to compile the app into the same site as the ASP site? 我的大问题是-除了制作ASPX页面外,我还需要将应用程序编译为与ASP网站相同的网站吗? I assumed I'd do that - deploy it there alongside the ASP Classic pages, and then just call the ASPX individually as needed. 我假设我会这样做-将其部署在ASP Classic页面旁边,然后根据需要单独调用ASPX。

Is this strategy sound? 这个策略合理吗? Do I need to do anything special for performance or configuration to make ASP Classic and ASP.NET coexist well? 为了使ASP Classic和ASP.NET良好地共存,我需要做一些性能或配置方面的特殊事情吗?

Thanks - this migration has been a bear because of the extreme asp classic dependency. 谢谢-由于对ASP经典的极端依赖,这种迁移非常麻烦。

It will work just fine. 它将正常工作。 I've seen it on several sites. 我已经在几个站点上看到了。 Just put them all in the same directory. 只需将它们全部放在同一目录中即可。

Your biggest issue will be that the ASP and ASP.NET pages will each have their own SESSION and APPLICATION variables which won't be shared between the two. 您的最大问题是ASP和ASP.NET页面将各自具有自己的SESSION和APPLICATION变量,而这两个变量将不会在两者之间共享。 If you are using session variables in either it can force you into doing a lot of hacks to make it all work together well. 如果您在两个会话变量中都使用会话变量,则可能会迫使您进行大量修改以使其全部正常工作。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Windows Server 2003 IIS呈现ASP.NET 4.0页为空白 - Windows Server 2003 IIS Renders ASP.NET 4.0 pages as blank IIS8上未加载ASP.NET页面(Windows Server 2012) - ASP.NET pages not loading on IIS8 (Windows Server 2012) 在Windows Server 2003上将ASP.NET 3.5项目部署到IIS 6 - Deploying an asp.net 3.5 project to IIS 6 on windows server 2003 服务器在IIS6上使用asp.net 3.5返回空白页面 - Server returns blank pages with asp.net 3.5 on IIS6 在Windows 7 ASP.Net页上的IIS上,CSS的显示不正确,如在Visual Studio 2010中的嵌入式服务器中 - On IIS in Windows 7 ASP.Net pages CSS is not show correclty as In the embedded server in Visual Studio 2010 将 ASP.NET MVC 3 (Razor) 应用程序发布到运行 Windows Server 2003 和 IIS 6 的远程服务器上 - Publish ASP.NET MVC 3 (Razor) app onto remote server running Windows Server 2003 with IIS 6 IIS 7.5上Windows 2003 R2 Enterprise上的Asp.net - Asp.net on Windows 2003 R2 Enterprise on IIS 7.5 hi。如何在Windows Server 2003的IIS6.0中部署Asp.net网站 - hi.how to deploy Asp.net website in IIS6.0 in windows server 2003 在服务器上编译ASP.NET页面 - Compiling ASP.NET pages on server ASP.NET Windows身份验证模式,IIS7和自定义错误页面-怎么样? - ASP.NET Windows Authentication Mode, IIS7 and custom error pages - how?
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM