Automate local IIS configuration

[blazingmind]

Most of us are using IIS Express because

1. it comes by default with VS
2. you only need to set up a port (and it is automated by PortSetter)
3. and select projects for running
   However there are some issues with it:
   it is believed that Express is not as robust as a ​local IIS​
   sometimes it messes up with debugging, by not loading symbols or shutting down the site if debugger detaches
   Some of us are using ​local IIS​. I've tried it as well, but I gave up since it required a lot of configuration, and beyond that it was affected by "hanging" bug, that me, @alpgurtan and @tony.yakovets currently experience. I only had a fix for this bug for IIS Express, so I switched back. However it seems that we are going to fix this bug soon.
   In order to use ​local IIS​ you have to turn it on in Windows features and then configure web-sites for each terminal and Hub. While you do that you specify a local address and a physical path to the dll
   However once you configure it - you have a more comfortable environment, since it is running separately from VS and it automatically updates the site once the new dll's are build
   And what is important is that you don't have to configure multiple startup in VS. Building terminals projects is enough
   I've spoke to Vladimir and he says that ​local IIS​ has an API, which is easy to work with from PowerShell. Also he claims that it shouldn't be hard to automate ​local IIS​ configuration by script
   Having that script will a) remove the requirement of setting multiple start up and
   b) will remove a need for running a PortSetter and re-opening solution
   Also while doing that he mentioned that he would like to change the way we handle our local addresses (what could be easily done as part of a script)
   so instead of "localhost:53249" it would be "http://localhost/terminals/docusign"
   the reasoning for that is:
4. it's not very polite to "eat" a bunch of ports on an external developers machine (what if his own app uses some of ports we do?)
5. it's more comfortable to see while debugging "http://localhost/terminals/docusign" instead of "localhost:53249"
   alexed 8:15 PM
   well, let's create a new issue to cover the scripting for iis. meanwhile, update the dev docs to explain the two choices and their ramifications
   I don't think the ports issue is that big a deal, but it would make things a little clearer. It might be good manners to do localhost/Fr8/terminals/docusign