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.

5,649 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.

    617 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...
      • Anonymous commented  ·   ·  Flag as inappropriate

        >> I don't believe only 1% of users use macros.
        Agreed. Probably the few people who leave "usage reporting" feature on are the ones who don't use macros.

      • Kevin HallKevin Hall commented  ·   ·  Flag as inappropriate

        I really enjoyed having the ability to spawn off command line programs and processing the text. This came in very useful for launching certain analysis programs with just a keyboard shortcut and having the output display in one of the output windows.

        We typically use this feature prior to code reviews in order to count lines and pre-process certain rule sets before sending the code to others. The feature was used by some individual developers to help launch external python-driven scripts too.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I don't believe only 1% of users use macros. Are MS sure that the reporting on the usage is actually working? I've not met a programmer yet that doesn't use them. Bring them back MS, I can't move from 2010 until you do.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I keep a 2010 version of VS around, just so I can go use this function to modify/edit code

      • Anonymous commented  ·   ·  Flag as inappropriate

        Can't believe you thought no-one would mind them being removed in the first place! As essential component for code editing. Massive thanks to Xavier Poinas for the 3rd party plug-in.

      • JJ commented  ·   ·  Flag as inappropriate

        Macros might make up 1% of my usage of visual studio, but it replaces 30% of my repetitive tasks.

      • Kevin FlanaganKevin Flanagan commented  ·   ·  Flag as inappropriate

        This. Record an editing operation, play it back as many times as you like. Simple, quick, incredibly useful. Totally needs bringing back.

      • Andrzej WłoszczyńskiAndrzej Włoszczyński commented  ·   ·  Flag as inappropriate

        Decisions made based on statistics (telemetry) are often stupid. I'm 50 years old and I have never used airbag in my car. Does that mean that airbags should be removed from all cars? Please add Ctrl-Shift-R / Ctrl-Shift-P (record/play macro) functionality.

      • Nathan PetersonNathan Peterson commented  ·   ·  Flag as inappropriate

        The removal of this feature is a perfect example of how Microsoft has lost its way. It reflects how out of touch it is with its customers. I have continued to use Visual Studio 2010 because of this and in some ways have been driven away from the Microsoft stack. Check out Sublime Text.

        VS2010 was probably the last (and best) usable version of Visual Studio. The entire wave of products that came after this release (VS2012, Windows8, Office 2013, and above) were worse than their predecessors. If possible, I use VS2010, Windows 7, and Office 2010. The last, good wave of Microsoft products. What happened? Did all the good people go to Google?

      • SagianSagian commented  ·   ·  Flag as inappropriate

        We used macros extensively. Bring macros back or we will have to roll-back to VS 2010.

      • Jeff RelfJeff Relf commented  ·   ·  Flag as inappropriate

        My C# macros, to automate Visual Studio 2013:

        Jeff-Relf.Me/Macros.HTM

        Yes, I had to rewrite my VS_2010 macros;
        but it's nice to have them in C# now,
        instead of "Visual Basic for Applications".

        Also, now I can write extensions too.
        Overall, it's been a wonderful improvement.

      • Dejan SeatovicDejan Seatovic commented  ·   ·  Flag as inappropriate

        Hi Microsofts
        I'm using visual studio since version 6. I have maintained and extended my macros for now almost 20 years. Now we have switched from 2010 to 2013 version, and the bat ("NO MACROS" WRITTEN ALL OVER) has hit me with such force that I almost lost my self.
        All documentation macros, debug directory assignment, adding and removing libraries (PCL, OpenCV, MATLAB, etc.), automation stuff and I really don't even know how many others are gone, forever. Useless!
        Guys, bring me my macros back. I was most productive using VS since ever, now I'm just a shadow of my self... Like Usain Bolt that has discovered that he has to run finals on Olympics with Ski-Boots his feet instead of spikes. Imagine that!
        PLEASE bring them back.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        Please provide a way to migrate existing VS 2008/2010 macros to VS 2012/2013/2015. We should not have to redesign dozens of existing/tested macros just because a new version of VS has been released.

      • Anonymous commented  ·   ·  Flag as inappropriate

        >The combination of Ctrl-Shift-R / Ctrl-Shift-P (record/play macro) was one of the most
        >productive features of old-day Visual Studio that give me ability to repeat
        >monotonic operations from keyboard. Please return it back
        Yes, I totally aggree.
        BRING IT BACK!!!

      • MaxMax commented  ·   ·  Flag as inappropriate

        The combination of Ctrl-Shift-R / Ctrl-Shift-P (record/play macro) was one of the most productive features of old-day Visual Studio that give me ability to repeat monotonic operations from keyboard. Please return it back

      • helmethelmet commented  ·   ·  Flag as inappropriate

        For macros I stiil use the VS6, best VS macro editor forever ... never hangs
        Please bring back this feature for non web developers (e,g embedded developement)

      • Anonymous commented  ·   ·  Flag as inappropriate

        Please bring it back! I often used Visual Studio keyboard macros (one in particular) dozens of times in a day, especially for variable generation. Removal of macro support is a very annoying inconvenience.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Please bring it back ASAP. Keyboard record/playback feature is such an important tool for most of us when doing refactoring. Currently I'm forced to use Notepad++ for this.

      ← Previous 1 3 4 5 30 31

      Feedback and Knowledge Base