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++.
Really nice, this is worthy of being a standard part of VS! Saw the vid, looking for how rollback would work but you mentioned you were wanting feedback on how that would work. In a perfect world I think the following would be nice:
a) Right click a file version and select 'restore file to current solution' b) Restore whole solution back to a given moment.
Aside from that, a couple of nice things to have would be: i) Permitting alternative diff tools (I use beyond compare). Or at least having arrows on the diff window to allow merging of the files.
ii) The option to run a command (and wait for the task to end) prior to the rollbacks - in particular I'd probably get it to do a quick zip file of the solution before the rollback occurs.
The extension does not interact directly with your chosen source code control system, so should work happily regardless of SCC choice. It watches changes made in the Visual Studio editor, and tracks them. So when you check a file in or out from SCC and edit it, the extension will note the changes you make because the file will have been opened and edited in Visual Studio.
I hope this clarifies how things work. We are looking at potential integration points with Source Code Control systems and would be interested to hear what sort of features you'd find useful there.
> 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.
I can't see how to, don't see anything in the blog post... I want to revert to an earlier version. I'd assume I would right click on the file I want to revert, select a version, and bam. the only thing I can see is to copy and paste text from the revision history, which is awful (formatting is terrible).
You have to do your rollbacks via the Diff View in the current version; we haven't implemented a feature to revert a file back to a previous version wholesale at this point.
At present the extension just lets you get back to the old code and copy-paste it to the file you want to revert. We do plan on adding reversion features in later releases - thanks for the feedback about how you'd expect these features to work.