I am using VS 2013 Ultimate. Installed the plugin, restarted and VS presents error "An exception has been encountered. This may be caused by an extension". Uninstalled the extension, restarted VS but the error does not go away. Very frustrating.
Awesome plugin. Don't usually comment about plug-ins, but this one deserved it. Makes looking back at file changes locally super easy without having to include git. A few times I've cut an entire class, and something happens where I loose that information, but the file still exists as an "Auto Backup", so AutoHistory saved my classes from my own demise!
It'd be cool if it could: A. Configure the location of the Auto Backup files B. The length it keeps the backups for C. Stay just as cool as it is now.
Include in the next update of VS, please!!! :) Very useful!! I´m a Technical Educator for Windows Internals and C++ (always using VC++), and I have to create groups of blocks of code to my samples and this kind of tool helps a lot.
Roger Villela Technical Educator for Windows Internals and C++.
Is there a way to add an entry to the context-menu of a file - "Auto History" and that will open a list of dates in which the file has changed, and then selecting one of these dates will provide a diff to the working version?
That's a good suggestion - thanks for bringing it up. Out of interest what granularity of change reporting would you want to see if there was such a list - since we auto-capture changes very frequently with this extension, I'm wondering if you would want to see something less granular - like 2x/day, 4x/day or similar.
> 2. the extension does not save your snapshots to disc until Visual Studio closes,
> so it is not a substitute for saving your work.
This sounds to me like that if I want to ensure that history is still available after a Visual Studio / Windows Crash I have to actual restart Visual Studio on a regular basis.
Is that correct interpreted?
Yes, for the current implementation if you want to ensure the snapshots are stored on disc, you'll need to close Visual Studio.
I'd continue to emphasize that this extension is not a substitute for any of the following:
1. Regularly saving your work
2. Regularly backing up your work
3. Using a source code control system
While other tool-windows on Visual Studio 2015 looks fine (probably because they resize GUI elements and position GUI elements relative to other elements) the tool-windows of this extension has all element interfering with each other
I think GUI layout must be changed to be resizable according to user fonts sizes.
I've been using this since soon after it was released. It's not a tool I use daily or even weekly but I do use it every once in a while. Because I don't use it often enough I can never remember how to actually compare anything with it. I often end up clicking on the little "bubbles" and up deleting them. I always have to go back and find a video about how it works. It's simply not intuitive that I have to drag part of the slightly off-color/shaded rectangle on the snapshots to determine when I want to compare against and then there's no indication that double clicking on the file name is what executes the compare. (and I'd also still like it to launch whatever compare tool the user has set up VS to use instead of VS's default)
I often edit my csproj files to customize the build process and last night Visual Studio suddenly started crashing when reloading project files back into the solution. No real error message except saying that Visual Studio has crashed and needs to restart. After restarting VS the project had been successfully loaded and built just fine, so I'm confident that there was nothing poisonous in the csproj.
I have quite a few extensions installed, so AutoHistory could possibly be conflicting with one of those, but as soon as I disabled AutoHistory the crashing on reload of a project stopped.
I hadn't really got round to trying the feature out properly but it looks like a pretty good idea.
At the moment, no. The awkward work-around is to diff the version you want, switch the diff window to the left view (so you get only the old source) and then copy and paste that into a new file.
The revert files feature, when it gets added (it is next of the list), will be able to revert deleted files.
As others have noted, I would love to see a "revert" feature, rather than having to copy and paste.
I also wish the window looked more like the Eclipse local history window (or the VS Local History extension: http://visualstudiogallery.msdn.microsoft.com/226c2108-9da9-407d-b90d-9783040d27b8), giving me a list of recent revisions for the currently selected file or files. The AutoHistory window seems to display only a single revision for each file, based on the earliest time in the slider on the left, which I find less easy to work with; if I'm looking for something I did about two hours ago, it means I have to move the bottom edge of the slider up and down carefully until I find the right time.
It looks like AutoHistory saves snapshots in some central location; the Local History extension saves them in the solution directory. There are pros and cons to both approaches; I'd like to be able to choose. I'd also like to be able to flush the snapshots on demand, or at some preset interval.
Thanks for taking a stab at this functionality; I'm hoping this extension continues to get some attention.