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,495 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.

    602 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

        >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.

      • Paul McCarthyPaul McCarthy commented  ·   ·  Flag as inappropriate

        One of the most common things put in a comment in code is the current date.
        Without macros I have to enter the date manually.
        The really annoying part is that the list of macros still shows. So it has not been removed but nothing happens when one attempts to run it. No matter what spin your PR department puts on it, THIS IS A BUG.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Maybe those 1% are your most productive users.

        Actually, I only use macros for one thing: to replace a feature removed from yet another version of Visual Studio, namely the option to stop compìlation projects once one project has failed. If Microsoft had left that as an option, I wouldn't need to resort to macros.

        Of all the user bases, surely developers are least likely to respond to well to this "Daddy knows best" attitude?

      • Phil RogersPhil Rogers commented  ·   ·  Flag as inappropriate

        No macros? Less than 1% use them? Well if nobody used them, that's ok, but I'm sure 1% is still a significant number. And those who use them probably use them a lot. Maybe the other 99% simply don't know about them.
        They worked, so why drop them? Leave them in for us enlightened few.

      • Michael RubinsteinMichael Rubinstein commented  ·   ·  Flag as inappropriate

        What were you thinking? I'm just switching from 2010 to 2015. I can, sort of, understand that you left it out in 2012. But I'm amazed that you haven't put it back in yet. Don't you folks write any code?

      • PJTraillPJTraill commented  ·   ·  Flag as inappropriate

        RE: MarkieMacro commented · April 21, 2015 5:33 AM

        ¿Surely you can use Tools–Customise–Keyboard for a shortcut to show/hide line numbers?
        Macros are needed when your commands include (specific cases of) variable arguments.

      • James CurranJames Curran commented  ·   ·  Flag as inappropriate

        What 'd really like (instead of or in addition to a proper macro language), is a simple FAST keystroke recorder.

        I'm assume that you dropped the macro feature because your telemetrics found that no one was using it, which I'll assume is because everyone realized what I did ---- when I needed a keystroke recording/playback, it was much, much faster to copy'n'paste the whole file in NotePad++, do the task there, and then copy the file back into VS

      • armen keshishianarmen keshishian commented  ·   ·  Flag as inappropriate

        Please bring it back, I don't know how what was the reason behind that, I red in some blog that only 1% of developers are using it, who did that investigation? no one asked me! ;) In almost every job that I had more than 75% of devs were using it and even more, enjoying it. So please bring it back.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Please, bring it back, we're losing too much time without macros... Microsoft have a macro system on near every product, visual studio is a programming software, put macro on it...

      • Anonymous commented  ·   ·  Flag as inappropriate

        Please bring it back, it is a pain to work without them and a consistent loss of time

      ← Previous 1 3 4 5 30 31

      Feedback and Knowledge Base