whidbey localhost/remote issue
I am pleased with the ease of creating aplications with VWD, however, it seems I have done something incorrectly...
client is running XP pro and VWD with framework2.0
server is running 2003 standard with framework2.0
I made sure the web properties were set to use the 2.0 framework, added the default.aspx to the documents list and enabled the default content page.
I created the web on XP (the client) and it is fully operational locally from the clients localhost; I can view it and browse successfully in a browser.
I decided it was time to copy the site to the server... no problem... then I tried to view the newly uploaded code... BOOM! page not found
I checked all the permissions, made sure the configurations were all accurate, and tried again, nothing.
ok... so, I decided to start all over. I created a empty web FROM the server console, and set all the permissions, etc... then I went to the client and tried to browse the new empty web, success (I allowed browse directory), I can see the vti folder and images folder... great I think.. until I try to copy the web into the empty web, now when I browse the virtual directory, it comes up as page not found (404) again.
ok... so, I decided to start all over... I will skip the details that I tried over and over for 2 days...
so, I take a different approach, thinking something might be wrong on my client... I created a new web FROM the server with VWD... cool, it works with no problem; the application runs and installs without incident and I can browse it with a browser... but only from the server; cannot view it from the client... it comes up as page not found, same as before.
I must have missed something someplace... I have used IIS many times, and dont seem to be able to find what I left out.
Any ideas?
TIA
--Harold
