CarlosRafi wrote
ckng:
You are not going to like this but in order to change the setup of DNN from a virtual dir to a dedicated Web site you did not have to reinstall or go through all that trouble. You only needed to create a new Web site and define its physical directory to the directory where you had DNN already, define the Host Header for the new site, and define the PortalAlias in DNN to match the Host Header. This would have worked. The Web.config would have connected to the same database with no problems (if it was working right before). Next time ask before performing major surgery 
.
Please tell us some details about your setup, what version of DNN, what version of SQL Server, is SQL Server on same box as the Web Server, do you have another Web site or application already running on the Web server at the URL you want to use for DNN?
Carlos
Thanks Carlos. Not too bad to hear that all it takes is simply pointing the web site's home directory in IIS to the location of DNN will do what I wanted. I suppose moving the files over would work as well?
I was trying to install DNN 4.5.1. My web server is Windows 2003 which also runs a bunch of other sites (all non-DNN, a mix of web sites on ASP 3.0 and ASP.NET 1.1). Right now they are all accessed via a different port number. (Internal development machine, so we don't really need "real" hostnames ;) ) SQL is on another box running good old SQL 2000.
Though I screwed up the thing I am still very curious to know what the DNN installation did that didn't allow me to reinstall without dropping the entire db - I've deleted every single table, stored proc, view, etc and even created the web site in IIS from scratch! Will ask my dba to recreate the db tomorrow and see how it goes. Thanks for all the help guys.
Regards
CK