How To - Various ways to setup multiple ASP.NET sites under a single domain

There are 3 primary ways to allow an ASP.NET application to run in one of your site's sub-directories:

 

1) If your site runs off one primary compiled .NET DLL, then simply keep all your .dll and compiled files in your site's root bin directory, and then you can use separate directories to run different parts of your application. The disadvantage to this method is you cannot create separate configuration files and your sub-directories will not run as completely stand-alone applications. However this should be sufficient for most cases and it requires no additional configuration.

2) Create a sub-domain from your control panel such as sub.mydomain.com. Then you can access the ASP.NET application at http://sub.mydomain.com. When you create a sub-domain in HELM, it automatically creates a new directory. So if you wanted to put an ASP.NET application in a directory called "myapp", then you would create the sub-domain from the control panel with the name set as "myapp.mydomain.com". Note that with this method alone you will not be able to access the application at yoursite/sub, but it will only be accessible by directly typing in the full http path to the sub-domain. This method allows you to run the files in the directory as separate applications and have separate configuration files.

3) Create a virtual directory from within Helm that points to the particular directory you need to run the ASP.NET application from. This method has the advantage of allowing you to access the folder directly instead of using a sub-domain. This method also allows your sub-folders to have separate configurations and run as a stand-alone application.