I have an existing ecommerce site written in classic asp. I would like to use Nuke for all the static content.  Moving the product lookup and cart funcitonality over is going to take a while.

I have the latest version (6.2.xx)  already installed on the server (IIS 7.5 2008R2) and am running a couple of sites on it already. I would like to avoid having to install another instance.

I think this might be more of an IIS question, but I figured this is a good place to start.

So how do I get a link on the www.mydomain/nukedefault.aspx page to resolve to www.mydomain/productlookup.asp given that thery are in differant folders on the server? 

I really just have some new content I want to add to the site for now, and another approach is to leave everything as it is and just do something like this - www.mydomain/nukecontent.aspx which would be much faster. I assume I would add the nuke folder as a virtual directory, but what would the portal alias entry look like? And the host header?

Hello MB,

If you just want to link from your DNN site menu over to the other site, you could also just create a page, for example "store" and then under page settings/advanced/other settings change the link type to URL (a Link to an External Resource) and place your link to the other site in there. You need to fully qualify an absolute URL when doing that.

Rich

For now I have my DNN site set up as a virtual folder off my main site so at least I can start moving some of my static content over. I will just add a link to the new folder.

so it's www.mydomain/nuke & it works fine

Next step -
What I would like to do is replace the bulk of the pages/menus/links in the existing site with DNN. But how would I set it up so that the www.mydomain.com is hosted in DNN? so it would be

www.mydomain.com/asp

I think I figured it out as I type this. I would just set up a new site in IIS using the IP currently in the dns (or a new one for that matter) and point IIS to the DNN install, then put my ASP stuff in a virtual directory. So the DNN links would just point to www.mydomain.com/asp/mypage.asp

Yes?