Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Mark Wilson-Thomas

Niner since 2011

I'm a Program Manager on the Visual Studio team, currently working on the Visual Studio Editor.  I've worked on developer tools for the last 8 years, including tools for Office, SQL and XAML. Prior to moving to the US I was a consultant in Microsoft Consulting Services in the UK on large scale projects.

  • Auto History Extension
  • Auto History Extension

    @Titti Skaria: the extension is now available for Visual Studio 2012 - see V1.2 :)

  • Auto History Extension

    VISUAL STUDIO 2012 SUPPORT NOW AVAILABLE

    Hi folks, I'm pleased to announce that by popular demand we have now made a version of the extension (1.2) available that supports both Visual Studio 2013 AND Visual Studio 2012. We hope this will allow more of you to try the extension and give us your feedback!

    Regards

    Mark

  • Auto History Extension

    Thanks @GlynP, yes you are totally making sense, we just need to work out how best to manage this slightly fuzzy line between the two worlds. We're thinking about it!

    Thanks for the feedback

     

    Mark

  • Auto History Extension

    Hi AutoHistory Extension Users

    PLEASE TELL US YOUR STORIES ABOUT USING THE EXTENSION!

    As you've had a little while to work with the extension now, we're really keen to hear any success stories you might have from using it - cases where you were able to get back to something you were doing, that would have been hard before for instance. Along with your suggestions for improvements, these really help us understand how useful the feature is to you. So tell us your stories about using the extension!

    Thanks!

    Mark

  • Auto History Extension

    Thanks @GlynP

    Our current thinking is we aren't really seeing Auto History as the means to migrate your code from one machine to another -  it really is something that sits between undo and source code control, and at this point we are thinking you'd want to use Source Code Control of some sort to check in a change set or similar, to move your work to your other machine. However your scenario is interesting, and we'll give it some thought.

    Mark

  • Auto History Extension

    Hi @GlynP: we've talked about the possibility of a roaming feature. It does present some challenges in terms of ensuring that the roaming is appropriately constrained (to avoid accidental Intellectual Property leaks in corporate scenarios for instance), and more significantly in terms of managing merge conflicts.  It could become quite confusing to use under these circumstances.

    @syyad - do you mean the capability to right click on a file listed in the file list of Auto History's window and see a listing of all snapshots that made changes to that file, with the ability to drill into those changes?

    Thanks for the continuing feedback

    Mark

  • Auto History Extension

    Hi @JohnLudlow and @Ibrody

    This is very useful feedback and all helps us to think about the future of this feature's design. It is definitely worth continuing the feedback, that's a big part of why we wanted to ship this preview so please keep it coming :D , UI, interaction, functionality - whatever will help make this idea more useful and useable in your daily work. Your comments on layout are definitely noted and we will give them some thought.

    @Ibrody, the snapshot restore including proj file diffs suggestion is a good one. If we had a "restore to this point in time across the whole project" we would certainly need to consider that. We are thinking about how best to weave this feature together with Source Code Control and would be interested to hear from folks where they would be interested to see it go. The most basic thought we have is around making snapshots stamped with any checkin changelists, but there's clearly more we could do.

    Mark

     

  • Auto History Extension

    Hi John

    We imagined that the extension would be completely hidden most of the time, and only used/viewed when the developer wanted to roll back - so we were thinking that a side-docked tabbed view would be a common usage pattern, hence the layout we chose. Do you think you'd want it always-visible?

    Thanks

    Mark

  • Auto History Extension

    Hello @Mark Harby

    The extension currently only tracks and snapshots files which are edited via the Visual Studio Editor. If an automated code generator uses the editor to do its work, then the edits will be snapshotted, otherwise they will not at present. I'd be interested to hear from users how important capturing snapshots for files like this is in terms of the usefulness of the extension to you.

    Hi @pm100: we are considering whether to provide a version of this extension that supports Visual Studio 2012 as well as 2013. We'll keep you posted.

    Thanks to all for your continued feedback!

    Mark

  • Auto History Extension

    Hi Everyone

    I have just updated the Gallery version to 1.1. V1.1 Fixes the issue with installation and load caused by strong name validation problems which folks have been seeing. Please try it and let us know how you get on!

    Thanks and sorry for the delay!
    Mark

See more comments…