I've seen several posts along the lines of "How do I install DNN into the root for an account at Godaddy" or other cheapo hosting provider.

I recently ran across an ASP.NET suggestion on redirection - to use Server.Transfer instead of Response.Redirect.  Quoting from http://www.developer.com/net/asp/article.php/3299641

Server.Transfer is similar (to Response.Redirect) in that it sends the user to another page with a statement such as Server.Transfer("WebForm2.aspx"). However, the statement has a number of distinct advantages and disadvantages.

Firstly, transferring to another page using Server.Transfer conserves server resources. Instead of telling the browser to redirect, it simply changes the "focus" on the Web server and transfers the request. This means you don't get quite as many HTTP requests coming through, which therefore eases the pressure on your Web server and makes your applications run faster.

Secondly, Server.Transfer maintains the original URL in the browser. This can really help streamline data entry techniques, although it may make for confusion when debugging.

That's not all: The Server.Transfer method also has a second parameter—"preserveForm". If you set this to True, using a statement such as Server.Transfer("WebForm2.aspx", True), the existing query string and any form variables will still be available to the page you are transferring to.

Since any installation of DNN will have access to the ASP.NET functions, is this not an easy way to accomplish the pseduo-installation of DNN into the root of a webiste - or at least make it seem to the outside world that such is the case?

If you have experience with this - or have tried it and would like to share your server.transfer code for noobs, please respond.

Thanks!