I have (finally!) been working through Issue 22 and in particular the moving a live DNN site live to a local environemnt. The tutorial has been very useful but it assumes that DNN is installed in the root of your site. For me my DNN part is installed in a folder on my domain name, i.e.

• Static pages, located as follows --> mydomain.com/index.htm, mydomain.com/red-widgets/index.htm, etc
• DNN pages --> mydomain.com/DNN-folder/Default.aspx, etc

So to replicate my full site on my local machine I need to copy down the static parts and the DNN part of the site.

The static parts for me are now installed locally and are fully navigable on:
http://localhost/mydomain/" target="_blank" rel="nofollow">http://localhost/mydomain/

A few points:

• These static HTML files are located on c:/inetpub/wwwroot/mydomain/ ).
• Note that I have not made the folder 'mydomain' a virtual folder but it is still perfectly navigable from http://localhost/mydomain/" target="_blank" rel="nofollow">http://localhost/mydomain/

On the other hand the DNN folder is now located locally at c:/inetpub/wwwroot/mydomain/DNN-folder/ This reflects the folder structure on the live site (i.e. 'DNN-folder' sites in the root of 'www.mydomain.com').

I am not sure what should be a virtual directory. SHould I make both 'mydomain' a virtual directory, in addition to 'DNN-folder'.

If we assume my site's (static) home page has a link to a /DNN-folder/articles.aspx page how do I then set up my local environemnt so that if I click such a link on http://localhost/mydomain/" target="_blank" rel="nofollow">http://localhost/mydomain/index.htm that http://localhost/mydomain/" target="_blank" rel="nofollow">http://localhost/mydomain/DNN-folder/articles.aspx will be correctly served up by the DNN app working on my local machine? Should I make both 'mydomain' a virtual directory, in addition to 'DNN-folder'?

For the moment when I try and access http://localhost/mydomain/" target="_blank" rel="nofollow">http://localhost/mydomain/DNN-folder/articles.aspx I get the following in an error message:

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. (the error then goes on to quote the line from the web.config about the machineKeys (validationKey and decryptionKey)).

I do not know if I have made myself clear, I can add more info if required!

Thanks

eoghano

Hello,

Good question, I have not set this up before but I would probably try the following:

Remove the virtual website of http://localhost/mydomain/DNN-folder

Setup 'mydomain' as a virtual website and then any folders within this should be incorporated into the website. - So in theory you should be able to enter http://localhost/mydomain/DNN-folder to launch your DotNetNuke portal.

Remember to set the correct folder permissions for your DNN installation files.

Let us know how you get on as it will be useful to know if this works,

Thanks,