Have set up similar for development using VS2010 and IIS Express on Windows XP - debug locally and then use publish wizard in VS2010 to copy required solution files to another PC on the network running multiple instances of IIS Express all on port 80 - the
main difference is IIS Express has to be run from a user account with administrator privileges to serve external requests or use a reserved port, and cannot be run as a service like IIS 5.1.
IIS Express references:
You will not be able to run IIS 5.1 and IIS Express on the same PC using the same port - they use the same httpcfg information and IIS 5.1 will have the port(s) locked before you can
start IIS Express - but if you are only using this on an internal network you can replace IIS 5.1 and run IIS Express with administrator privileges for your old asp.net websites. But you can restrict IIS Express/IIS 5.1 to listening on specific IP addresses
(httpcfg set iplisten) and use Apache or another web server on port 80 on a different IP address.
If you edit your applicationhost.config file you can also set the binding information for each instance of IIS Express and using host names you can run a multi tenant version of Orchard:
<site name="old.south-league.com" id="1092685870">
<virtualDirectory path="/" physicalPath="Z:\Inetpub\website\old.south-league.com" />
<binding protocol="http" bindingInformation="192.168.1.35:80:old.south-league.com" />
<site name="cms.orchard.net" id="864892907">
<virtualDirectory path="/" physicalPath="Z:\Inetpub\website\cms.orchard.net" />
<binding protocol="http" bindingInformation="192.168.1.35:80:cms.orchard.net" />
<binding protocol="http" bindingInformation="192.168.1.35:80:cms.south-league.com" />
<binding protocol="http" bindingInformation="192.168.1.35:80:cms.northamptonhc.org.uk" />
A shortcut/command can be used to easily start selected website;
"C:\Program Files\IIS Express\iisexpress.exe" /config:"Z:\Inetpub\IISExpress\config\applicationhost.config" /site:cms.orchard.net
The shortcut/command window remains open - in version 1.0 of Webmatrix you could start an instance of IIS Express and close the window and use the system tray to stop IIS Express processes, but that option was removed
in version 2.0 - you can still use the system tray but closing the window will now terminate the IIS Express process.