Enable Local History
As we investigate this proposed model, we have a general question for you.
1. We support Undo stacks in the tool.
2. There is an extension “auto-history” that provides a level of automatic roll-back, based on heuristics/events to perform snapshots
3. Local repo support.
If we think of the above as a continuum from simple undo to a more explicit commit, we would like to hear feedback on how you’d prefer a model for local history support on this spectrum. E.g. is the preferred model to allow automatic snapshotting to a local repo?
Extension does not support VS2017 and Undo is buggy when used with quick actions (almost lost contents of the file after "Create declaration / definition" that I wanted to undo). Other IDEs do not touch local repo to provide this functionality (example: all tools from JetBrains).
Joseph Jaspers commented
I agree, the history functionality is sub-par at best. I personally enjoy Netbeans History functionality. Netbeans gives an option to view history and revert back from previous version. The history even saves across uses (As compared to the undo-stack mentioned which is limited to each individual startup). Likewise, the history function showcases what changes you made to assist in helping to view which revert you want.
Thanks Mike and other commenters. I'm also interested to hear from folks about their alternate strategies to cope with the lack of local history in VS (assuming you're not already trying the extension). Some folks have mentioned use of a local git repo and frequent branching/committing as a means to solve the problem, for instance. Please do drop me a line at mwthomas at Microsoft dot com if you have feedback on this sort of strategy, on the usefulness of the extension or on the local history concept as a whole.
I used this feature in Eclipse while writing an Android app and it really grew on me. Completely automatic and no more lost code. Was nice being able to do a diff to see what I had changed from 30 minutes or even a day ago. Giving this one 3 votes!
IT's very important i usually put project for this aim in dropbox folder to have a chance to rewind to that point where i made smth wrong.. If it was in vs it would be wonderful.. There is a lot of moments when version control systems is useless and cant do nothing ((
What do folks make of the Auto History preview? Would it provide the capabilities you've been voting for here?
Supporters of this feature may be interested to see the new Auto History Preview Extension... check out http://blogs.msdn.com/b/visualstudio/archive/2014/01/23/auto-history-extension-in-visual-studio-2013.aspx and let us know what you think...
Eric Lewis commented
I would LOVE to have this as I am working on a new file that is not yet in TFS and have no way of getting back to an earlier version. I can not check it into TFS yet because it will have issues with other things.
Local history feature is very important. as other editors such as eclipse, phpStorm etc support. Why not visual studio ?
Marko Ilievski commented
People can also make mistakes which can affect the source control, so this can be a real life saver.