Using Virtual Directories doesn't allow you to keep anything separate, the reverse is actually true.
You can't put port numbers in your hosts file. That's not what it is for.
If you create a website in IIS, and add the binding as I have suggested, you will end up with a website that is totally separate from others on your server.
- Create a folder somewhere on your server
- Create a new Web Site in IIS and name it mojoportal
Set the "Physical Path" to the path of the folder from step 1.
Set the "IP Address" to "All Unassigned" and the "Port" to "80".
Set the "Host name" to "www.cheeseburger.com" (without quotes)
Click OK
- Click the "Application Pools" item on the left side of IIS Mgr.
- Click the "mojoportal" application pool and then click the "Advanced Settings" link in the "Actions" pane.
- Set the ".NET Framework Version" to "v4.0," make sure the "Identity" is set to "ApplicationPoolIdentity" and click OK
- In Windows Explorer, move the files from your current mojoPortal installation to the folder you created in step 1. Put the files directly inside of the folder, not inside of another folder. In other words, if the path to your folder is c:\mojoPortalDev, all of the files from the release would be found inside of that folder. So, you should be able to go to c:\mojoPortalDev\bin and see a bunch of dlls files.
- Right click the folder from step 1 and choose properties, on the security tab click Edit..., then click Add..., now type "IIS AppPool\mojoportal" (without quotes) and click OK, click OK, click OK
- Repeat step 7 on the /App_Data and /Data folders but this time, the "mojoportal" user will already be there and you just need to change the permissions on these folders to "Modify" for the user.
The use of a hostname on the site will allow you to create multiple IIS websites, using the same port and IP address, on one server.
Now, add this to the hosts file on your local pc:
<SERVER IP ADDRESS> www.cheeseburger.com
I've been using IIS for over 16 years (since version 1). I can guarantee you that the above steps will work (not withstanding firewall settings). There is nothing in this configuration that is unique to mojoPortal. This is how one would create a standard website in IIS. The only thing that is not what you would do for a public website is the use of the hosts file. But, since you do not have access to a DNS server and a true domain name, we have to use it.
HTH,
Joe D.