It is easy to run multiple ASP. NET Website applications on a virtual host.

I don't know if any of my friends will encounter such a problem as I do:
Buy online.. NET Space. Due to the limitations of virtual hosts, you cannot set a directory as an independent application or a relatively high-price space. Although you can set it, the quantity is also limited. This problem causes the website to be relatively passive when it expands its independent functions. It is also troublesome to want to run several applications with different functions under a website.

However, recently I found a very simple method that can be cleverly avoided. To put it simply, there are two points:

Uniform bin directory:

All generated dll files and files to be referenced are stored in the bin directory under the Application root directory. The only problem is that the Application name must be unique, the advantage is that a unified Common module can be called.

Uniform Web. config configuration file:

This is the second step. Copy the configuration files of different applications to the Web in the Application root directory. in config configuration, including connectionString and appSetting, copying them to their respective nodes also results in naming problems, and compared with the dll file naming problems, conflicts are more likely to occur.

After completing the preceding two points, you can place independent Web applications in your favorite subdirectories to run them independently.
In general, it is very practical to avoid naming issues.