So I have decided to roll out DNN to replace our company current static intranet. My question resolves around what is the ideal method for deploying DNN. My current intranet has over 20 .Net applications that I still plan on using. My options as I see them are: 

1. Create a new virtual dir. within the current live web site within IIS and then when I am ready with the switch I change the home directory of the site to point to the DNN folder. That way I believe the existing .Net apps can be launched using simple URL links from DNN.  (this seems like the way to go but I want to see if anyone else sees a problem with this)

or

2. Create a new web site within IIS and use a separate port while setting up DNN. When I am ready to go live I would need to move the .Net apps over to the new web site.

Thanks in advance for any advise and/or constructive opinions.....

Or even better, 4.  Add a second IP address to the server and use that for a new site in IIS with DNN.  You can still reference the .NET apps on their existing site and never need to move them.

Jeff