From:http://blog.csdn.net/jh_zzz/archive/2010/08/18/5821241.aspx
Recently, when doing some web research, I basically do not use IIS, IIS Express is very convenient, because the current beta version, some of the functional interface is still invisible, online information is very small, so I put my previous experience to write out.
The first reason to focus on IIS Express is that you want to deploy one of our products to Windows XP Professional, and you know that the price and Pro gap for 2003 server is still large, which has a significant impact on product profitability for high-volume deployments. Because we use MVC in development, this is in the XP Pro IIS5.1 on the deployment, on the one hand the program to do the corresponding processing, but also need to deploy URL rewriter things like that, quite troublesome, solve the server costs, I'm afraid it will bring the cost of developers travel.
With IIS Express, the problem can be solved in its entirety, with a major focus on the following issues:
1. Allow Remote access
2. To be able to support the creation of virtual directories
3. Can support running multiple WEB application
4. Our product is in the school LAN deployment, performance should meet at least dozens of people concurrent requirements
1. Installation Deployment
Download Address: http://www.microsoft.com/web/webmatrix/, IIS Express is published with the Web Matrix, after installing the Microsoft Web Platform Installer, you can select Install IIS Express (the English version has IIS Express to choose from, the Chinese version directly selects the Web Matrix).
The introduction can refer to Scott Blog: http://weblogs.asp.net/scottgu/archive/2010/06/28/introducing-iis-express.aspx
IIS Express overview:http://learn.iis.net/page.aspx/868/iis-developer-express-overview/
Running the Web Matrix from the Start menu automatically starts a Web site by default, and the management interface is simple enough to create a directory as a Web site directly.
Actually, when I use it, I basically run it on a command-line basis, and I use only the following parameters:
iisexpress [/config:config-file] [/site:site-name] [/systray:boolean]
Profiles can be modified directly based on the default profile, and the profile used by default is in [My Documents]/iisexpress8/config/applicationhost.config
My current usage is to simply package the Web Matrix's directory on a CD-ROM, configure files to be published with the application, and then create two batch files to start and stop the IIS Express service, which is very handy, and the batch content is probably like this:
Start: Start f:/projects/microsoftwebmatrix/iisexpress/config:f:/projects/xxx/applicationhost.config/systray:true/ Site:mtloraldemo
Stop: taskkill/f/im iisexpress.exe/t
Other machines do not need to install the Web Matrix at all, as long as the. Net framework is installed to run directly.
2. Remote Access settings
Found in the configuration file sites/site/bindings is bound to the localhost 80 port by default, and binding to the specified IP address is possible if other machines are required to access it.
3. Virtual directory settings
This is similar to the following:
I tried too many virtualdirectory nodes, but found that the WEB application was not working, and that multiple virtual directories were not using separate web.config, which were later resolved through configuration application.
If the site has something like spring, there will be an error at run time, please configure ApplicationPool to Clr2classicapppool.
4. Configure Multiple Sites
Multiple sites as long as the configuration of multiple site nodes can be, the specific configuration is similar, but multiple sites need to use a different port.
If you need to run multiple sites at the same time, add a few more modifications to the batch process, which is equivalent to running multiple IIS Express instances at the same time.
5. Performance Test Results
The following tests were done, and the performance of the test results met the requirements:
1. Wrote a simple test page, using load Runner 200-way concurrent pressure test, for 2 hours.
2. Formal product deployment, our products run a total of 9 IIS Express process, listening to the 8080~8089 port, our entire department dozens of people at the same time to simulate the user visit the site and actual use.
This article from Csdn Blog, reproduced please indicate the source: http://blog.csdn.net/jh_zzz/archive/2010/08/18/5821241.aspx