Hello,I have been talking with my host company concerning the possibility of either getting a subdomain or another domain hosted on the same server in order to support a non dotnetnuke compliant application that is written for the .net framework but not specifically moduler to integrate into the dotnetnuke framework.Now my question is this dotnetnuke is installed on the root area of the host I have. When I inquired concerning adding sub domain or another domain in order to run two web applications (one being dotnetnuke framework and the other being a shopping cart not written specifically for dotnetnuke) I told them about the problem of having nested web applications and how the web config of the parent dotnetnuke would conflict with the web config of the shopping cart if it wasn't written as a moduler dotnetnuke instance.Now they said that would you could do is do an add on of a sub domain and or other domain and though by default it would point to the root of your account (where dotnetnuke framework resides) it is possible to via a little coding redirect the sub or other domain to another directory within your hosting account and have it act as the defacto root of your domain or subdomain.Now the question I have is as follows: Since dotnetnuke resides at the root of my site hence in essence all subfolders being within the framework in this situation would it be possible for me to do as the host provider suggested and have an add on sub or regular domain redirected to a specific folder manually created within the root of the account (or where dotnetnuke resides) without getting dotnetnuke server errors because the added folder doesn't conform to dotnetnuke rules.I guess what I am trying to say is if a directory becomes a defacto root of a sub domain or regular domain does that mean it is like its own root and isolated from the way the dotnetnuke framework implements things so that I could create a link to this store application within dotnetnuke but not have this store app actually written for the framework.I ask this because I really like this particular shopping cart witten for the .net framework but not dotnetnuke and I like the idea that if for some reason I opted to not use the framework or worked on a .net site where another framework was in use I could be able to be more portable with this store that wasn't created under the moduler style of dotnetnuke.Thanks for your help in this inquiry and I hope you understand what I am trying to get at here Thanks againBo