I don't know if I had the option to install the IIS configuration on a different port. But the first thing I did after installation was typed http://127.0.0.1/ Into my browser to see the site and nothing happened.
After looking at the IIS configuration I noticed it was setup to listen on 8080. I am fine with this as I can change it if desired.
The problem that at the end of the install you are asking yourself where do I go next. It might be nice to have an option to launch the website after installation in a browser to continue the setup process.
The IIS installer code checks for existing sites on port 80, if there is one then it defaults to 8080, if that’s in use then it goes to 81 and keeps incrementing till it finds an free port. It does have greyed out hint next to the port that tells you if port 80 is in use, perhaps I should make that more obvious. The other thing is that the installer creates the
We’re still working on the installer… part of the problem is that the service takes too long to startup on the first run, as it’s creating the database schema etc. I have managed to run through the installer, and install an agent, point a browser at the site and the main service is still not up… not what we want the user to see.
The issue is NHibernate, it is taking a long time to configure itself… currently investigating ways to speed this up, and also how to get the service to startup a maintenance mode service on the first run etc…