I keep getting errors that it does not like using port 7000.

Is there a way to change so that http://localhost:7000/ becomes http://localhost:whogoes/

 <sites>
   <site name="Development Web Site" id="1" serverAutoStart="true">
     <application path="/">
       <virtualDirectory path="/" physicalPath="c:\webconnectionprojects\whogoes\web" />
     </application>
     <bindings>
       <binding protocol="http" bindingInformation=":7000:localhost" />
     </bindings>
   </site>

What I can find something in above needs to be changed but I have not figured out a change that works.

What are you doing exactly and where are you seeing this information? This looks like a Visual Studio local configuration file and the reason you're seeing it in Visual Studio most likely is due to IIS Express usage that was configured for port 7000.

If you're using IIS Express you have to use a specific port - you might be able to force port 80 but I suspect you'll run into problems with that with conflicts or IIS proper if installed conflicting.

+++ Rick ---

When I load my exe up to my server on line, will it work like version 7 even though on my local machine is using port 7000.

Thanks,

Jim

Yes. You can think of localhost:7000 as just being a different domain name.

As long as you don't hardcode any request links or paths with absolute Urls that include the scheme and domain (ie. https://localhost:7000/subfolder/somepage.wc (bad) vs. ~/subfolder/somepage.wc (good)) everything will work the same.

The additional bonus over Web Connection's original approach of using virtual paths is that you can more easily use a root path and aren't required to run in a subfolder like /wconnect in development and then use the / root for a live site.

+++ Rick ---