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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Problem with Subdirectory Application in DNNProblem with Subdirectory Application in DNN
Previous
 
Next
New Post
1/20/2011 10:54 AM
 
I have inherited several web applications at my new job that are DotNetNuke v4.09 on the .net framework 2.0.
I have been tasked with adding a simple .net web application as a subdirectory to one of the sites.  The application
is very simple; single page, no third party controls and the web.config file only needs a connection string section and
I built it on the 2.0 framework, too; that's it.

I of course had multiple errors that I will not post, but after searching the web I have found from several sources, 
including DotNetNuke.com that adding the <location path="." inheritInChildApplications="false" > will fix the problem. 
It did, the subdirectory application now works, but there is another issue that I have not found anyone else to have.  

After logging into the main DNN site, go to any module that uses the Telerik RadEditor and click the pencil - edit icon and
an error message will be displayed that the RadEditorDNN requires the script manager tag.  I know that by wrapping the
<system.web> and <system.webserver> sections in the web.config file with the <location> tag prevented the main application
to reach the Telerik subdirectory.

So, the question is this:  How can we make a subdirectory application work in the DNN world without breaking any other subdirectories ?

Thank you in advance for any help !
JW
 
New Post
1/20/2011 12:23 PM
 

as you know web.config settings are inherited in subapplications of a root site. The 2 ways to control this are by disabling the inheritance

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

If you want the majority of settings to be cleared then you can use the clear attribute to clear them and then add the required ones in granularly.

<httpHandlers> 
      <clear/> 
</httpHandlers> 


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/20/2011 1:42 PM
 
Thank you for the quick response.  I am on the same page as you.  Currently trying the <clear /> and the <remove /> and this is what I have thus far.
This is the web.config from the sub application.  The main web.config is the standard DNN web.config after install. It has not been modified except for adding an additional connection string. 

I tried the <clear /> method first in each section and ended up with an error in stating, "No http handler was found for request type 'GET'". And, not knowing each and every element needed for a web.config file, I figured I would simply <remove /> entries that referenced DotNetNuke.  Now the error is, Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.  and this is the same error as when I first placed the subdirectory into the DNN environment.

JW


~~~ sub application web.config ~~~

<configuration>
<appSettings>
    <clear/>
</appSettings>
<connectionStrings></connectionStrings>
<system.web>
<compilation debug="true"></compilation>
<httpModules>
<remove name="Compression"/>
<remove name="RequestFilter"/>
<remove name="UrlRewrite"/>
<remove name="Exception"/>
<remove name="UsersOnline"/>
<remove name="DNNMembership"/>
<remove name="Personalization"/>
</httpModules>
<httpHandlers>
<remove verb="*" path="*.captcha.aspx"/>
<remove verb="*" path="LinkClick.aspx"/>
<remove verb="*" path="RSS.aspx"/>
<remove verb="*" path="Logoff.aspx"/>
</httpHandlers>
<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>
</pages>
</system.web>
<system.webServer>
<modules>
<remove name="Compression"/>
<remove name="RequestFilter"/>
<remove name="UrlRewrite"/>
<remove name="Exception"/>
<remove name="UsersOnline"/>
<remove name="DNNMembership"/>
<remove name="Personalization"/>
</modules>
<handlers>
<remove name="LogoffHandler"/>
<remove name="RSSJandler"/>
<remove name="LinkClickHandler"/>
<remove name="CaptchaHandler"/>
</handlers>
<validation validateIntegratedModeConfiguration="false"/>
</system.webServer>
</configuration>

 
New Post
1/20/2011 5:30 PM
 
Is the issue occurring in the root website or the child application? Can you check and make sure that both sites are using the same version of .net (i.e. .net 3.5sp1 or higher) as child applications should not impact their parents (the hierarchy flows down, not up).

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/20/2011 9:49 PM
 
The error occurs from the root site. If I put in the <location ... > tag in the root web.config, child site works, but Telerik breaks.  Take <location ... >
out and child site does not work. 

Both sites are .net 2.0, but the child site was developed in VS 2010 and compiled in the .net 2.0 framework so it would match roor site.
I do not know if that makes a difference ot not. The child site has only one page, no third party controls or references.
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Problem with Subdirectory Application in DNNProblem with Subdirectory Application in 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