Howdy,

Getting ready to deploy DotNetNuke on our site and we have 3rd Party ASP.Net applications. If I have a sub folder in my DotNetNuke folder structure with these applications in it will this cause a problem with the applications or dotnetnuke? I'm slightly concerned as they have web.config files that go along with them.

Thanks,
Owen - http://www.fdwsnetworks.com

Good question, Owen.

I will certainly be running into a similar predicament/question from one of my clients in the next few weeks. It's a survey application called SelectSurveyASP from classapps.com.

Joe, Lee... Any bits of sage advice/warning before I start exercising my vocabulary of obscenities - and possibly inventing a few new ones - while attempting this? I can't speak for Owen's vocabulary [laugh]

I haven't experimented with this so its one of those situations where you will have to try it and see what happens. - The only advice I would give is BACKUP everything before carrying out any tests.

Thanks guys,

I have been fiddling with this and it doesn't look like it will work. Dave if your using an asp application then I don't think it really should be a problem. I've used asp applications without any issue and using iFrames. Also not sure what kidn of survey application that is, but you might want to direct them towards a DotNetNuke survey program. Or check this out http://www.helferlein.com/DotNetNuk...ault.aspx.

The problem that I'm running in to is that with ASP.Net applications that use a web.config the DNN web.config takes presidence over the other applications' web.config. I found this work around which might actually help you, but it doesn't help me because my applications whilst .Net are written in ASNA Visual RPG Language for .Net http://www.dotnetnuke.com/Community...fault.aspx

So my issue is how do I make DotNetNuke ignore sub directories? Is there something I can add to my web.config to say "Ignore this folder called applications" so that it will exclude from execution with DNN's web.config. The only thing I can think of to get this to work is to make them a totally separate site, bt that means spending the extra money to change the SSL security certificate in my situation.

Thanks,
Owen - http://www.fdwsnetworks.com

If you have asp.net applications in folders underneath DotNetNuke, then they will (I think) try to inherit from the DotNetNuke web.config file.  You may have to have something like this in your application's web.config file (note that I added spaces around the < and > so they won't be interpreted):

    < pages >
      < namespaces >
        < remove namespace="System.ComponentModel" / >
        < remove namespace="System.Data" / >
        < remove namespace="System.Data.SqlClient" / >
        < remove namespace="System.Drawing" / >
        < remove namespace="Microsoft.VisualBasic" / >
        < remove namespace="System.Globalization" / >
        < remove namespace="DotNetNuke.Services.Localization" / >
        < remove namespace="DotNetNuke.Entities.Users" / >
        < 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 >

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

    < httpHandlers>
      < remove verb="GET" path="FtbWebResource.axd" / >
      < remove verb="*" path="*.captcha.aspx" / >
      < remove verb="*" path="LinkClick.aspx" / >
      < remove verb="*" path="RSS.aspx" / >
    < /httpHandlers >

--------------
I think that you have just keep doing this until you've eliminated everything that has to be eliminated to make your application worl.  The code above was taken from a working website.

Thanks Joe,

That will help quite a bit, it won't quite work with the 3rd party applications because when they send and update (which they do quite frequently it seems) it will over right these. But it will help with other apps that I have which are no longer supported.