Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Adding a virtual directory to DNNAdding a virtual directory to DNN
Previous
 
Next
New Post
1/23/2008 11:09 AM
 

My company wants to have a page on our corporate site that is totally different from the look and feel on other pages. I tried creating a virtual directory named "test" and gave it read access, etc. A screenshot of the properties is at the end.

After I did that I created a Default.aspx page that is extremely basic (just is a Hello World, html at bottom).

Once I did that, I went to the page... and it then immediately redirected me to the site's homepage. I really, really need to get past this road block and I'm hoping there's a way. Any ideas?

Thanks!
Andrew

Default.aspx code

<%@ Page Language="C#" %>

<html>
<head>
<title>ASP.NET Hello World</title>
</head>
<body bgcolor="#FFFFFF">

<p><%= "Hello World!" %></p>

</body>
</html>

 

 
New Post
1/23/2008 12:07 PM
 

I believe your issue is that DNN's HttpModule is intercepting your call, and redirecting to the main site.  You will need to clear DNN's HttpModules in your virtual directory's web.config.  It is the same procedure as setting up a virtual directory for a web service, as this blog post from Chris Hammond talks about.

Let me know if that works for you,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
1/23/2008 12:08 PM
 

I was actually able to figure it out based on some older threads...

  1. Create application for the virtual directory
  2. In the web.config file there's gonna be a number of changes...

Within <pages>...

        <namespaces>
          <remove namespace="DotNetNuke.Services.Localization" />
          <remove namespace="DotNetNuke.Entities.Users" />
          <remove namespace="DotNetNuke" />
          <remove namespace="DotNetNuke.Common" />
          <remove namespace="DotNetNuke.Data" />
          <remove namespace="DotNetNuke.Framework" />
          <remove namespace="DotNetNuke.Modules" />
          <remove namespace="DotNetNuke.Security" />
          <remove namespace="DotNetNuke.Services" />
          <remove namespace="DotNetNuke.UI" />
          <remove namespace="DotNetNuke.Entities.Portals" />
          <remove namespace="DotNetNuke.Common.Utilities" />
          <remove namespace="DotNetNuke.Services.Exceptions" />
          <remove namespace="DotNetNuke.Entities.Tabs" />
        </namespaces>

This is what my <httpHandlers> looks like:

      <httpHandlers>
        <remove verb="*" path="*.asmx"/>
        <remove verb="*" path="*.captcha.aspx"/>
        <remove verb="*" path="LinkClick.aspx"/>
        <remove verb="*" path="RSS.aspx"/>

        <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
        <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
        <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/>
      </httpHandlers>

This is what my <httpModules> looks like:

      <httpModules>
        <remove name="UrlRewrite" />
        <remove name="Exception" />
        <remove name="UsersOnline" />
        <remove name="DNNMembership" />
        <remove name="Personalization" />
        <remove name="Compression"/>
        <remove name="RequestFilter"/>
      </httpModules>

After those changes, my page was able to work flawlessly.

 
New Post
4/10/2008 3:23 PM
 

Hi ,

This is really  interesting. Are you able to run Both applications ? i mean DNN  portal as well as the Page  that you  have added after  making changes in the Web.Cofig file.

Could you please  be more  detail on this?  Me  too trying to call custom .aspx  pages  inside DNN portal but not  sure  about how to proceed further as i  am new to DNN

Any help will be appreciated

Thanks

Vijay

 

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Adding a virtual directory to DNNAdding a virtual directory to DNN


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out