I suggest you ...

Bring back Macros

I am amazed you've decided to remove Macros from Visual Studio. Not only are they useful for general programming, but they're a great way to be introduced to the Visual Studio APIs.

If you are unwilling to put in the development time towards them, please release the source code and let the community maintain it as an extension.

4,642 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    cpmcgrathcpmcgrath shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared a merged idea: Macros on debugging  ·   · 
    Todd CarterTodd Carter shared a merged idea: Bring Back Macro Support in VS 2012  ·   · 
    WaldyrWaldyr shared a merged idea: Bring back the Macros support on Visual Studio  ·   · 
    under review  ·  Visual Studio TeamAdminVisual Studio Team (Product Team, Microsoft) responded  · 

    We are currently reviewing the feasibility of delivering a scripting capability in a future version of Visual Studio. Please continue to offer your comments on what scripting capability we should offer while we research this suggestion.

    Tony Goodhew, Program Manager, VS Pro.

    526 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        Just upgraded from VS2008 to VS2013. Missing at least two features:
        - Macros were used daily.
        - Find Symbol.
        Definitely need them back.

      • Jim NicholsJim Nichols commented  ·   ·  Flag as inappropriate

        Macros were a huge part of my development process. The ability to not only record a macro but create a toolbar button for it aided me EVERY DAY!!!! Macros should be just as much of a part of Visual Studio as they are in Office.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I've read that Microsoft removed Macros from Visual Studio, because their statistics showed that it was not an oft used feature. I can tell you, I did not use it often myself, but when I did find a need for it, it made a HUGE impact and cut my work load down by many times.

        Because a feature is not often used does not equate to its importance.

      • Anonymous commented  ·   ·  Flag as inappropriate

        How about making Python the Scripting language of VS :D It'd be good for these vb script guys to learn something new ;)

      • Toby SharpToby Sharp commented  ·   ·  Flag as inappropriate

        A very very useful subset of macro functionality would be a simple record & playback function for repeated keystrokes. This might not require full scripting.

      • Ramesh KadambiRamesh Kadambi commented  ·   ·  Flag as inappropriate

        I think this was the dumbest idea by Microsoft Visual Studio Team. I have a whole suite of tools that facilitate commenting code and generating documentation written as macros which are unusable in visual studio 2013. Please put it back.

      • WaldoWaldo commented  ·   ·  Flag as inappropriate

        I would like to request that you PLEASE provide macro capability in VS. I am converting legacy VB6 code (finally!) to VB.net, and really need this functionality. Meanwhile, I will be forced to cut/paste into Word to use Word macros to help me out. Tragedy given the world class IDE provided in VS 2013.

      • Mike JonesMike Jones commented  ·   ·  Flag as inappropriate

        yes, bring back macros. I used them often to do repeated editing.
        Was very useful for creating consistent comment blocks
        I can't over emphasize who useful macros are.

      • Kevin CrokeKevin Croke commented  ·   ·  Flag as inappropriate

        I am now wishing I left sending usage data on. I wonder if there is a correlation with people who use macros and people who turn off sending usage data. That 1% really does seem low.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Please bring macros back in Visual Studios.... I don't always use macro's often, but when I do, I prefer VS macros ... Keep coding my friend.

      • JKoppJKopp commented  ·   ·  Flag as inappropriate

        Please bring back macros to Visual Studio 2013.
        I used them a lot to accelerate daily usage, e.g. to attach the debugger to running processes via hot key.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Serious veteran coders use macros to do amazing things. If they aren't used it is because most people don't know about them, but the tremendous benefit to those of us who do cannot be ignored. Why take out something that was already written. Even if you remove the GUI for editing, why remove the record/replay feature? Simple record/replay gives me 98% of everything I ever used keystroke macros for

      • Anonymous commented  ·   ·  Flag as inappropriate

        The macro record-keystrokes and playback are an invaluable time-saver in special editing situations.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        Yes, bring it back. Special the record and play function.
        1% procent uses macros that means 99% does not now what they are missing.

      ← Previous 1 3 4 5 26 27

      Feedback and Knowledge Base