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 ...Combine Existing Classic ASP pages with New DNN Site?Combine Existing Classic ASP pages with New DNN Site?
Previous
 
Next
New Post
12/7/2008 8:01 PM
 

I've got an existing classic asp web app site.  This site serves two purposes.  It is the face of my business.  And it also serves up reports for my clients.  Currently the site is setup like this:

Home Page/Face of my business: www.mydomain.com

Client A acceses his web app here:  www.mydomain.com/clientA/

Client B acceses his web app here: www.mydomain.com/clientB/

ETC...

I want to move my hope page over to DNN, but keep the classic ASP web app stuff available to my clients (at the current address if at all possible).

I'm guessing that there is no way to mix and match a DNN site with classic ASP pages.  If not, I considered a subdomain like webapp.mydomain.com.  This would allow me to easily separate my DNN content from my classic ASP content.  I have a few problems with this approach:

1)  All of the links that already exist on the web that point to the various parts of the client's web app are now broke.

2)  How does relocating all of these client apps to a subdomain affect the search engine results for my main site?  I currently have VERY good search engine rankings almost always placing me at the top or near the top of the search results, but if I separate out in to a domain and subdomain, would my rankings drop becuse most of my clients will link back to a subdomain instead of my primary domain?

3)  If I were to do this, I'm assuming some type of redirection at the IIS level is what needs to be done.  Any ideas on this?

Thanks in advance for any tips you guys can offer!

 

 

 
New Post
12/8/2008 3:04 AM
 

you should be able to install DotNetNuke in the root and include your existing apps into virtual directories, mapped as subfolders (but physically located outside the DNN installation folders. you might need to modify the web.config files mapped into it, to prevent inheritance from DNN web.config settings.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/8/2008 4:16 AM
 
 
New Post
2/4/2009 11:39 AM
 

Shesh, I thought I had checked the notification box so that I would get notified if anyone responded to my question!  Didn't get no notification.  =)

Virtual directories was the key.  I set those up for each client in my dnn root site and all works good.  Even server side includes are working fine between different virtual directories.  Just wanted to say thanks for the info guys and confirm that YES, the virtual directory thing for some classic asp pages works great!

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Combine Existing Classic ASP pages with New DNN Site?Combine Existing Classic ASP pages with New DNN Site?


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