DotNetNuke的部署和单独的ASP.NET应用程序一起 - 可能存在的问题？ [英] Deploying DotNetNuke and separate ASP.NET Application together - Possible Issues?

问题描述

我提出这一个积极的尝试来阻止可能由此产生的潜在问题。的情况是，我们正在开发一个客户端，它会处理来自其客户网上订购ASP.NET应用程序。此应用程序将使用相同​​的数据库，他们目前的WinForms应用程序使用（在这里没有真正的问题）。

I am making this in a proactive attempt to head off any potential problems which could arise from this. The situation is that we are developing an ASP.NET application for a client which will handle the online ordering from their customers. This application is going to be using the same database that their current WinForms application uses (no real issue here).

与此同时，我们为他们开发使用DotNetNuke的一个新的前端网站。 DotNetNuke的应用程序将简单地链接到ASP.NET应用程序为客户提交他们的订单（无需为他们来回沟通等）

At the same time we are developing a new front-end website for them using DotNetNuke. The DotNetNuke app will simply be linking to the ASP.NET application for the customers to submit their orders (no need for them to communicate back and forth, etc.)

该计划是在客户端的位置主办同一个盒子两个应用程序。我所寻找的是这将美元两个应用程序夹住的p $ pvent可能发生的冲突（web.config文件冲突等），潜在的问题或设置提示是否有具有的相同位置都举办了问题，应该如何IIS设置起来，等等？

The plan is to host both applications on the same box at the client location. What I am looking for are potential problems or setup tips which would prevent possible conflict between the two apps (web.config conflicts, etc.) Is there a problem with having both hosted on the same location, how should IIS be set up, etc.?

如果有任何外部资源，也可以它可以解决这个问题，请随时向他们以及链接。

If there are any external resources also available which could address this, please feel free to link them as well.

推荐答案

选项1：让所有的应用程序单独的虚拟目录关闭根网站。然后有根文件重定向到为该网站（DNN）的默认应用正确的子目录。搜索结果
选项​​2：（DotNetNuke的根，在子目录其他网站），将会有一个web.config中继承的很多问题，如果新的应用程序不与DotNetNuke的建成，但你可以通过阻止根web.config继承绕过这些。基本上你添加以下到你的根Web.config（DNN）文件。

Option 1: Make all the apps separate virtual directories off of the root website. Then have the root document redirect you to the proper subdirectory for the default application for that website(DNN).

Option 2: (DotNetNuke in root, other site in subdirectory) There will be many issues with web.config inheritance if the new application is not built with DotNetNuke, but you can get around these by blocking inheritance of the root web.config. Basically you add the following to your root web.config(DNN) file.

<location path="." inheritInChildApplications="false">
    <system.web></system.web>
</location>

选项3：正如斯科特说，建立独立网站与子域名不同的充，并将它们链接在一起。你可以设置一个重定向使whatever.com/order发送用户order.whatever.com。

Option 3: As Scott said, create seperate sites with differnt subdomains and link them together. You can setup a redirect so whatever.com/order sends a user to order.whatever.com.

这篇关于DotNetNuke的部署和单独的ASP.NET应用程序一起 - 可能存在的问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！