CBAutoSave has been updated

Version 1.11.2 is available.
New in this version:
– When AutoSaveDocuments is selected, the files are saved in such a way that other extensions (such as Trailing Whitespace Visualizer) will be able to participate in the Save operation.

The extension is now up-to-date in the Visual Studio Gallery, so I am removing it from the private gallery.

Unfortunately, I haven’t yet figured out how to update an extension in the Visual Studio Gallery (now called the Marketplace), so I have put the latest version in my private gallery:
http://www.cbates.net/VSIX/atom.xml.
(In VisStudio: Tools->Options->Environment->Extensions and Updates, add the URL shown above to the list of “Additional Extension Galleries”.)

After I added the custom gallery, both VS2013 and VS2015 recognized that a newer version of CBAutoSave was available.


Version 1.11.0 is available.

Unfortunately, something happened to the update process in the Gallery; I ended up removing version 1.10.0 in order to upload 1.11.0, so 1.11.0 might not appear in Tools->Extensions and Updates->Updates.

New in 1.11.0 is the ability to run simple commands when a Document window or Visual Studio loses focus.
USE WITH CAUTION — the command must be available and capable of being run via
DTE2.ExecuteCommand();

cbautosave

You can specify a command to execute when a Document window loses focus, and a command to execute when Visual Studio loses focus.

(Fwiw, I got so used to  having this in gVim:
au FocusLost,TabLeave * call feedkeys(“\<C-\>\<C-n>”)
that I got a little obsessed with finding a way to make it work in VisStudio.  Fortunately, Jared Pared (VsVim author) added the VsVim.SetMode command.  Thanks for that!)


The new version will be 1.10.0.
I have added an option to save an individual Document when its tab/window loses focus.

Update:  New version is now in the Visual Studio Gallery (as well as the private gallery).


The new version is in the private gallery, and will be uploaded to the Visual Studio Gallery “real soon”.

(I’m getting this error trying to upload the .vsix to the Gallery:
“If you see this page, it is because an error occurred in the system while trying to process your request. We apologize for the inconvenience. This error has been reported to our team for analysis.”)

16 Comments

  1. Visual Studio updated to 1.11.0, but now with the new version I can’t close Visual Studio. Instead of closing, Visual Studio displays a popup windows with the message “Value cannot be null. Parameter name: value”. I using Visual Studio 2015 Update 3.

  2. 1.11.4 is not letting me close Visual Studio 2015 Update 3 as well…

    I uninstalled and reinstalled a few times but it still says: “Value cannot be null. Parameter name: value” when I try to exit.

  3. On a fresh OS +VS install I got also “Value cannot be null. Parameter name: value” when I try to exit VS,a fix is to go to VS Tools-Options-Cb AutoSave -General and focus (empty) options fields,then press OK button.From now on Cb AutoSave works fine,there must be some null values that cause the problem and VS options will put empty spaces instead of nulls
    thanks

  4. I was also having the “Value cannot be null. Parameter name: value” issue.

    I fixed it by going into the CBAutoSave options, and setting all the options to True (AutoSaveProjects, AutoSaveSingleDocument, AutoSaveSolution). After that, it worked fine. I was able to set them back to false as well, and the issue hasn’t reappeared (so far).

Leave a Reply

Your email address will not be published. Required fields are marked *

Are you human? * Time limit is exhausted. Please reload CAPTCHA.

Protected with IP Blacklist CloudIP Blacklist Cloud