添加独立的ASPX / ASMX页到DotNetNuke的 [英] Adding independent aspx/asmx pages into DotNetNuke

问题描述

你好，我刚安装的DotNetNuke 5.06我的服务器上，也就是说，路径mydomain.com/dnn~~V

Howdy, I just installed dotnetnuke 5.06 on my server, say, the path is mydomain.com/dnn

我有库独立的DotNetNuke的，我要运行，它包含了，所以我还没有尝试过将它集成到DNN，只是还没有Web服务和其他各种HttpHandlers的。该库位于下mydomain.com/dnn/lib

I have a library independent of dotnetnuke that I have to run and it contains web services and various other httphandlers so I haven't tried to integrate it into DNN just yet. the library is located under mydomain.com/dnn/lib

图书馆工作的罚款我跑5.04旧服务器上，一切工作正常，但由于某些原因，我与5.06（Windows 2008中，SQL Server的IIS 7.5）新安装返回404，当我尝试下MYDOMAIN / DNN访问一个页面/ lib中/，无论它是ASPX，ASMX ......然而似乎图像工作得很好，一切要么返回404或重定向到DotNetNuke的Default.aspx的。这从来没有与我的旧网站以前也发生过。

The library worked fine on my old server running 5.04 and everything worked fine, but for some reason my new installation with 5.06 (windows 2008, sql server, iis 7.5) returns 404 when i try to access a page under mydomain/dnn/lib/, regardless of whether it's aspx, asmx...however images seem to work just fine, everything else either returns 404 or redirect to default.aspx in DotNetNuke. This has never happened before with my old site.

没有人知道我在这里失踪？任何的建议是大大AP preciated。

does anyone know what I'm missing here? any suggestion is be greatly appreciated.

推荐答案

其实，这个问题被固定只在DNN 5.6.2，这是目前处于测试阶段。 5.6.1版本仍然有这个问题。还有，在任何情况下工作的解决方法：绝对URL添加到您的PortalAlias​​表。你必须用手工做到这一点，因为门户选项卡不允许别名根在同一级别为现有的别名。

Actually, the issue was fixed only in DNN 5.6.2, which is currently in beta. Version 5.6.1 still had this issue. There's a workaround that works in every situation: add the absolute url to your PortalAlias table. You'll have to do this by hand, because the Portals-tab doesn't allow aliases that root at the same level as an existing alias.

另一种解决方案的，如果你不能等待新版本的DNN，包括添加以下code到 RequestFilterModule.vb 和 UrlRewriteModule.vb ，其中恢复现有的行为。这不是唯一的应用到DNN 5.6.2修复，因为程序员相信这是太大影响性能检查每一个访问文件是否存在（我认为奇怪，因为一些文件在每次访问感动，无论如何，主DNN缓存使用基于文件的缓存和在一般情况下，数据库的访问比文件访问是较慢）：

Another solution, if you can't wait for the new DNN version, includes adding the following code to the RequestFilterModule.vb and UrlRewriteModule.vb, which restores the existing behavior. This is not the fix that's applied to DNN 5.6.2, because programmers believe it is too much of a performance impact to check for file existence on every visit (which I consider odd, as several files are touched on every visit anyway, the main DNN cache uses file-based caching and in general, database access is slower than file access):

'Add this to the RequestFilterModule.vb (line #59)'
'and to UrlRewriteModule.vb (line #325)'
If File.Exists(app.Server.MapPath(Request.Url.LocalPath)) And Not _ 
   Request.Url.LocalPath.ToLower.EndsWith(glbDefaultPage.ToLower) Then

     'exit early when path is an existing path'
     Exit Sub
End If

显然，如果应用此修复程序，你必须要小心DNN的一次更新。

Obviously, if you apply this fix, you have to be careful with the next update of DNN.

这篇关于添加独立的ASPX / ASMX页到DotNetNuke的的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！