Chris.  Thanks for your reply.  Yes, created new website (not virtual directory) within IIS, mapped to c:\dotnetnuke folder, added dotnetnuke hostname in system32\drivers\etc\host file with appropriate entries.  Yes, all webs works fine in browser, including all webs in localhost and those of separate webhosts configured in IIS.  Curious of why Visual Studio "lost" the Project's Mapping to IIS of existing project(s)?  I found workaround just now, I have to create "new" projects to connect to existing projects to get it back.  This is interesting.  Hmm ...

Bob Davis.

Chris.

Yes, correct.  None of the paths changed. Why do tons of extra maintenance work. There was no need to change all those paths and projects I have in Win7 dev machine built with VS, IIS, SqlExpress, "the works machine hehe", etc. 

Interesting though.  Hmm...

Used the 5.2.3 install zip, unzip to c:\dotnetnuke folder, added website IIS, gave unique hostname, added same hostname to system32\etc\host file, verified all existing current webs in localhost, unique websites hosts (local), and local dotnetnuke with web browser, each and everyone of these works fine. 

Only issue is that VS "lost" all path information to all existing projects for both localhost and unique websites hosts (local).  Workaround is to "build" new sites on existing web(s) and thus build "new projects".sln 

Thank you for your assistance.  Let me know if you experience similiar situations or other or no issues discovered.

Bob Davis.