Well, why would you want to, for starters? It is a recipe for catastrophe to immediately push changes based on saving, and kind of feels like it would be counter-productive to have both a local and a live version of the code.
However, if you really feel it’s a good idea to immediately have changes up at the server, I’d suggest either
1. Work directly against the server using SFTP. I believe most development tools worth their salt should be able to handle that or
2. Look into the various tools that allows you to “watch” files, and write a script that when it detects a change in the file, it immediately copies it over to the server using whatever method of copying you are comfortable with.
A better way is to use some kind of version control (git seems a good fit seeing how you mention github), and go live with the changes once you’re at a nice and safe place and has properly committed.
@Melindrea: I don’t want to upload code manually. I just want to develop everything online. So..
Right now I am using WinSCP / Filezilla but both have manual functions.
WinSCP is good that we can open file directly in DW but still I want localhost once saved it would reflect at server/website code.
I’m still not sure I follow. Do you want to have a copy of your website on your harddrive, while working on the server, where the local version should be identical? Or are you wanting to have no copy locally, but preferably work in Dreamweaver with the files that are on the server?
At any rate, you really should rethink this, especially if you are working on clients’ sites. Have you ever broken things so badly that the site isn’t even coming up? I have. However, I was working on a local copy, using a git repository, so it wasn’t a problem to deal with it. That’s not going to be the case if you’re saving the changes directly to the live site.
If what’s annoying you is needing to select which files to upload after you’re done testing the changes and are satisfied that they are correct and that the tests run correctly, then I would suggest looking into something like make, rake or grunt (depending on what flavours you like).
Unfortunately, I don’t do windows (I’m a linux gal), so I can only give you the theories behind what to do if you’re still sure that you know what you’re doing.
1. Find yourself something to monitor file changes ([this gem](http://rubydoc.info/gems/win32-changejournal/0.3.3/frames) looks decent)
2. Create a script (make, rake, grunt… something along those lines, not sure what kind of shellscripts you could use on Windows) that when ran will synchronize the changes to the server.
3. Consider if you _really_ want to do this
4. Write a script that based on file changes (using the file monitor in step one) runs the script in step two
Kutec, I think the others here have given you some valuable advice; but, if you just have a simple web page (HTML, CSS, JS only), you can try out Dropbox (you start out with 2Gb of free space). When you save your file in your local dropbox folder, it automatically uploads the changes to your Dropbox account which can be loaded in your browser like a live preview.
If you’re feeling generous, use [this link](http://db.tt/xSbdG51) to sign up for Dropbox using me as a referral, so I can get an additional 500Mb :P… you can get up to 16Gb of free space (500Mb per signup).