Configuring local IIS and VS self-brought IIS

The previous debug Web site has been using the VS comes with IIS, as learning is not much of a hindrance, but if used for team project development will bring a lot of inconvenience. Team development projects have a unified website port number, file directory, port number can be modified in the configuration file is not what, but to build a virtual file directory in their own project map to the server, using VS comes with IIS can not be done, only with the local IIS.

The above two pictures are to add a Web site virtual directory

Okay, nonsense. Say, the following problems and solutions

1, if the site with VS comes with IIS boot, the system will automatically create a port for this site

Location of this file: C:\Users\r-\Documents\IISExpress\config\applicationhost.config

If a port number conflict occurs, you can modify it here. Note: This is the port number used by the Vs-iis startup

2, the port number in the Web site configuration file must be and the port number that is used when the local IIS is created has been

    <webprojectproperties>          <Useiis>True</Useiis> <!--If you are using local IIS, change this to ture, and if you use Vs-iis here to false--          <Autoassignport>True</Autoassignport>          <Developmentserverport>9000</Developmentserverport>          <Developmentservervpath>/</Developmentservervpath>          <Iisurl>http://localhost:9000</Iisurl> <!--up and down two port numbers all the time, and using local IIS, the port number on the local IIS has been--          <ntlmauthentication>False</ntlmauthentication>          <Usecustomserver>False</Usecustomserver>          <Customserverurl>          </Customserverurl>          <Saveserversettingsinuserfile>False</Saveserversettingsinuserfile>        </webprojectproperties>

Note: Different sites will not load

3, how to configure the site in the end is to use Vs-iis or local IIS

Right-click the solution for your website--Properties

The virtual site here is the address of the website for example: http://localhost:9000

4. Deploy the MVC Web site on IIS and open the post-extensionlessurlhandler-integrated-4.0 workaround

An MVC Web site is deployed on IIS, open after 500 error: Handler "extensionlessurlhandler-integrated-4.0" has an error module "Managedpipelinehandler" in its module list

Here's how to fix it:

Register with the administrator to run the following command:

32-bit machine:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe-i

64-bit machine:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe-i

That's it, personal experience, unofficial, wrong place to look.

Reprint Plus Source: http://i.cnblogs.com/EditPosts.aspx?postid=4763902

Wish: Beginners Learn smoothly!

Configuring local IIS and VS self-brought IIS