Deploying asp.net application to root directory in

Question

How can I deploy an asp.net application to the root of an IIS6 webserver? All the applications I've deployed before have been in directories, such as http://www.example.com/app1/. To deploy that for the first time, I've always just gone to the IIS manager, and selected "Create Application" in the properties for that folder.

Now I'm trying to create an application on the root of the web site, like http://www.example.com/. But the property pages are different, and there doesn't seem to be an option to create an application in the root directory.

This is probably very simple, but I can't figure this out.

Answer 1

The application settings are on the "Home Directory" tab of the properties for the site (right click on the root node for the site and select properties).

Answer 2

The very simple way is to access your application by just typing URL as 'localhost':

open the IIS service -> sites -> default web site -> (r8 click)->manage web sites-> advanced setting

Now it will show new window;

1) imp: select the physical path: (now change this path to your app's path): e.g. my path is: C:\Users\Mahadev\Documents\visual studio 2017\Projects\WebApp\WebApp

So probably hope your path will like this and select this. in this path folder names likely App data, App start, bin.. so on

2) Physical path credentials: click on this and select 'specific user' and give OS user name password. now click 'OK'

Answer 3

You should create new site instead of creating new web application or virtual path on (Default web site).

1. Right click Add new website
2. Type your site name, select physical path point to your deploy web site and notice type your domain name in host name label: Ex: www.example.com (your domain must be existed). Then click OK.

This way will make your web application root path "/" .

Answer 4

The root folder is already an application - no need to create one. You deploy the same way - the folder is just "/" instead of "app1/".

Answer 5

What Paul said. Big gotcha is that, if there are already applications running in virtual directories (eg /App1), there can be a little bit of configuration war as the base configuration settings override the app's settings, resulting in either outright crashes or (worse) unexpected behavior.