Bug ... or feature?
If you are using Visual Studio to edit remote files, VS needs a "hard save" to trigger a transfer from local cache to remote file.
Right now, I use the following process to get VS to save to remote file store once a file has been updated outside of the editor.
This example is using Web Essentials less/css generation, but this is true for any similar process.
- update .less,
- save all
- reload when message comes up that a file has been modified outside of the source editor
- go to the .css file
- add a space to a line
- save all again (this triggers VS2012 to update remote file)