DotNetNuke和定制开发 [英] DotNetNuke and custom development

问题描述

我们正在考虑在很短的时间内购买DotNetNuke（或Sitefinity），而且我有一个问题，我无法找到一个快速的答案。 （

We are considering purchasing DotNetNuke (or Sitefinity) on pretty short notice and there are is a question I have that I am having trouble finding a quick answer to. (I have a separate but similar post with Sitefinity as the focus, if you can answer that better or in addition.)

我们目前正在使用没有使用任何CMS，我们有一些自定义开发，不会消失，因为我们去与一些或大部分的网站CMS。

We are currently not using any CMS at all and we have some custom development that will not go away just because we go with a CMS for some or most of our site.

我们的定制开发是c＃ASPX与站点主站和嵌套的站点主页。这些自定义应用程序在我们的网站中没有自己的顶层，但是是分支的一部分，通常是一个或两个层次（例如，http：www.contoso.com/branch/app/default.aspx）。

Our custom development is c# ASPX with Site Master and nested Site Master pages. These custom apps do not own their own top level in our web site, but are part of a branch, typically one or two levels down (for example, http:www.contoso.com/branch/app/default.aspx).

• DotNetNuke如何在CMS /自定义混合模式中进行配置？例如，是DotNetNuke安装在网站的顶部，或者在需要在网站下。


• 在混合CMS和自定义网络应用程序时，这是如何相关的？


• CMS界面是否允许添加这些自定义应用程序，还是只需转到Web服务器并将其添加到结构中？


• 从阅读其他帖子，我们可以创建自己的自定义c＃模块，并有CMS编辑器放入页面上的模块。有人可以为我确认吗？

• How is DotNetNuke typically configured in a CMS/Custom "mixed mode"? For example, is DotNetNuke installed at the "top" of the web site, or "where needed" down in the web site.
• How does this relate when mixing CMS and custom web applications?
• Does the CMS interface allow for adding these custom apps or do you just go to the web server and add them to the structure?
• It appears from reading other posts, we can create our own custom c# modules and have CMS editors "drop in" the modules on the pages. Can someone confirm that for me?

如果我没有提供足够的细节，请随时询问更多。

If I did not provide enough detail, please feel free to ask for more.

推荐答案

DNN最常安装在网站的根目录，但不是必需的。它有时作为一个虚拟目录中的应用程序运行，它是较大站点的一部分。

DNN is most commonly installed at the root of the website, but that is not required. It is sometimes run as an application in a virtual directory that is part of a larger site.

可以在DNN中的正确位置添加.aspx页面。 UrlRewrite处理程序最初将查看所有这些请求，并假设现有页面和友好的URL处理程序不认为他们拥有.aspx页面，DNN将停止处理请求并将其传递到您的页面。没有具体的方法用DNN注册这些页面。我不会一般推荐这种方法，但它可以工作，并在特定情况下有意义。

It is possible to add .aspx pages at the correct location within the DNN. The UrlRewrite handler will initially look at all such requests, and assuming that existing pages, and friendly url handlers don't think they "own" the .aspx page, DNN will stop processing the request and hand it to your page. There is no specific way to "register" these pages with DNN. I wouldn't generally recommend this approach, but it does work and can make sense in specific situations.

或者，您可以编写自己的DNN模块。现有的代码，通常可以很容易地通过转换代码工作在继承自PortalModuleBase的.ascx用户控件中。希望利用核心DNN特性的代码。成员资格或权限当然需要修改才能使用DNN API。

Alternately, you can write your own DNN modules. Existing code, can usually be quite easily be adapted by converting the code to work in .ascx user control that inherits from PortalModuleBase. Code that wants to take advantage of core DNN features e.g. membership or permissions will of course need to be modified to use the DNN APIs.

DNN模块方法通常是最好的选择。但是你的情况的细节可能使其他方法更适合你。基本上只要你的站点被布局，以便清楚哪些请求注定为DNN，哪些不是，你可以根据需要与其他asp.net代码混合和匹配。

The DNN module approach is generally the best option. But the details of your situation may make one of the other approaches more appropriate for you. Basically as long as your site is layed out so that it is clear which requests are destined for DNN and which are not, you can mix and match with other asp.net code as needed.

这篇关于DotNetNuke和定制开发的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！