Menu
Working with Visual Studio 2010 here, but the behavior has been the same since the dawn of time - is there a way to force the IDE to automatically save the project file after doing an "Include in project" on new files? Folks new to VS don't quickly get in the habit of Ctrl+Shift+S after every one of these operations, leading to multiple repo commits when we discover assets missing from our bundled webapps.
735
By default, VS Code requires an explicit action to save your changes to disk, Ctrl+S. However, it's easy to turn on Auto Save , which will save your changes after a configured delay or when focus leaves the editor.
To turn on or turn off the Auto Save feature in Visual Studio Code, go to File and click on Auto Save from the drop-down menu: The steps are completely the same in Windows and macOS. If you want to config the Auto Save behavior deeper, go to: Mac: Code > Preferences > Settings.
I used to run into this all the time and it was very annoying. The solution that I use is to re-map CTRL+S to File.SaveAll since I'm already using source control. However, this doesn't help new VS installs that haven't had this set up.
200
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
