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 ...web config issueweb config issue
Previous
 
Next
New Post
1/26/2007 11:16 PM
 
 

We have upgraded to dnn from an old asp cms system

as part of our company website the were several sub domains that run .net 1.1 apps.

so for example we had www.ourcompany.com/vault/vault.asmx

these other services  are mostly web service in nature. the problem we are having is that the dnn website is working fine but all the other apps have stopped. when they are called instead of reading the web config ie for vault like the example above it is reading the web config for dnn which is in the higher root. when it is reading the web config it is failing on the required permission setting which think is new to 2.0 and the virtual folder is set 1.1

so how can i get iis or dnn to know that it should be reading the config file for vault in this example and to ignore the dnn website config. the issue of course is that dnn is version 2.0 net and our vault software is 1.1

i know that i could change and create a whole new website in iis and have a different dns entry so vault.ourcompany.com but that is not an ideal situation.

i hope i have explained the issue. any help on this would be appreciated

 
New Post
1/27/2007 3:26 AM
 

You will need to mark the Vault folder as an application in IIS. Once this is done, IIS will start using the web.config located in that folder. However, you will then be faced with a new problem. The impact of HttpModules/Handlers loaded through web.config is cumulative in a hierarchy of web applications. As a result, you will have to copy many of the DotNetNuke assemblies into the Vault applications "bin" folder even though they are not being used. This is due to the way ASP.Net processes web.config files.

I am not sure if ASP.Net 2.0 and 1.1 apps can be mixed in a hierarchy, but in theory it should work. If not, you should consider flagging the Vault app as 2.0. Most ASP.net 1.1 apps will work without changes under 2.0.

Nik

 


Nik Kalyani
Co-founder
DotNetNuke Corporation
Blog | Twitter | FaceBook
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...web config issueweb config issue


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