I have a DNN 05.06.02 site set up by itself in a web site (not the default web site).  The Web Site name in IIS is "DNN Public Site".  The DNN Application is configured one folder below this as "/DNN" with the DNN files installed in that folder.   Because of this, in my Host Settings, the "Relative Path" shows as "/dnn".

All of my URLS on the site look something like this:
http://<domainname>/dnn/Home/tabid/...

I want to eliminate the /dnn relative path and have everything in the root of the site.  Is it as simple as this?

- Back up the DNN files
- Delete the site and application from IIS
- Create a new root folder for the site
- Restore all the files from the /dnn subfolder and below to the root (one level higher than before)
- Create an Application at the root of the site named DNN
- Edit the PortalAlias table values to the new settings

Running Windows Server 2008 R2 64 bit.

I'm afraid I'm missing something.

Thanks,

Steve

Philip,

Thanks for the reply.  I tried it and ran into a problem.  My DNN site is NOT in the default website.  I'm running IIS 7.5 on Windows Server 2008 R2.  Unless I'm missing something, I can't create an application at the root of the website.  It wants to create a folder under the website for the application.

Is there any way around this if the site is not in the default web site?

Thanks,

Steve

Robert,

Wow....  I can't believe I couldn't see that.  That's a great solution.

I'm still missing something, though.  When I do it either your way, or my long and tedious way, I can't execute any ASPX code at all.  Even a simple test ASPX file fails with a 404 error.  As long as I leave the DNN subfolder as an application, everything works fine.

I've been looking at AppCmd.exe to check IIS settings and the default application on the root of the site seems ok with the correct Application Pool.

I'm about out of ideas as to why ASP.Net fails without that "DNN" application in place.

Thanks for your help!

Steve