I am trying the simple and basic develop (and test) locally, and do not publish on the remote through a dial-up ISP until everything is debugged.
This is simple, right?
I have configured the testing server (on my home computer) as C:\Inetpub\wwwroot\FHSDevelopmentSite\ (adding the extra file), while "remote info" is an ftp dial-up: ftp.filename.com
Well, in this configuration, I am able to publish great. The problem is that Dreamweaver thinks my remote ISP is the testing server. Whenever I make a development, experimental, or debugging change, Dreamweaver tries to publish every change like it is doing an auto refresh at the remote server.
I DID NOT check "refresh remote file list automatically," and Dreamweaver is taking liberties to refresh at the ISP anyway. If I happen to be logged-on while I make a debugging change, such as "alert('hello');", that change will be published automatically, before I have tested it on the testing server.
Dreamweaver seems to have reversed the role of testing and remote server.
Could anyone please help me? What am I doing wrong?
As a temporary work-around, I am completely turning-off the remote-info and telling Dreamweaver that my local computer is the remote, and I write the same information in both testing and remote information. Temporarily, I am able to author my website locally. I am doing the uploads with WS_FTP LE.