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,990 votes
Sign in
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
cpmcgrath shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

We’ve heard your feedback loud and clear, and we’ve been working on a solution. We’re therefore very happy to announce that we’ve now released a version of Macros that supports both Visual Studio 2015 and Visual Studio 2013.

While we were at it, we took the opportunity to fix a couple of bugs and improved the keyboard shortcuts.
We hope you enjoy it.

For more information, see the blog post here: http://aka.ms/vsmacros

We’ve also open-sourced the code under the MIT license. If you have any suggestions or contributions, feel free to create an issue or a pull request in the new GitHub repo: http://github.com/Microsoft/VS-Macros

Justin Clareburt
Senior Program Manager
Visual Studio Extensibility Team


Sign in
Password icon
Signed in as (Sign out)
  • Wesley Kenis commented  ·   ·  Flag as inappropriate

    this is not even 10 percent of what you had in the past. This is just as much rubbish as it can get. I do a find and replace and guess what I find in the macro dte.ExecuteCommand("Edit.Replace");


    the only interesting ida is that it is an extension and nog yet another source interwoven screwup. I'm GETTING THIS PIECE OF **** OFF MY MACHINE.

    I'm better of not having this lame excuse use resources.

  • Sero commented  ·   ·  Flag as inappropriate

    But they return it as extension! They changed convenient CTRL+SHIFT+R & CTRL+SHIFT+P for stupid CTRL+M,R & CTRL+M, Enter but it works anyhow))))))

  • Roger Sprague commented  ·   ·  Flag as inappropriate

    I have just moved from VS 2010 to VS 2015 and quickly realised that macros are missing.

    Please bring back CTRL+SHIFT+R & CTRL+SHIFT+P as a standard product feature of VS.

  • Sagian commented  ·   ·  Flag as inappropriate

    It would seem that the ball has once again been dropped on macro support. There have been no updates on the plugin. We have rolled back to VS2010. VS2017 is on the horizon and will stay there unless full macro support is reintegrated.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Really I don't care if the macros are in JS, VBS, or any scripting language.
    Actually JS manes some sense as more development uses it, but the fact that VS2015 relies on some open source sub-standard plug-in which is considerably inferior to what they had decades previously says enough about MS.

  • Bakra commented  ·   ·  Flag as inappropriate

    This is what I'm talking about !! The title CLEARLY STATES:"Bring back Macros".

    But noo....some person over at microsoft (probably some nine-to-five-with-kids types or a desperate-to-please H1B or a Google reject) sees this as a golden opportunity to polish his resume.

    In he comes knowing nothing about the original macro feature. The original feature that could do so many things (eg. change the title bar's text etc. etc.), for him, is equal to this mere bagatelle he is forcing on us.

    Devil is in the details...this can't be repeated enough times in today's society.

  • Frank commented  ·   ·  Flag as inappropriate

    Macro with Javascript is simply ridiculous! So we're back in 1980 or what? Why can't you just leave an extremely excellent programming model like VB.NET in VS 2010 as it is?? So that developers can take over their macros to VS 2015 and simply continue their work. Never ever will I give up my VS 2010 and consider VS 2015 as an appropriate successor. No chance! Not acceptable at all!

  • Paul commented  ·   ·  Flag as inappropriate

    Excellent start! Now let me put them on my toolbar with a custom icon, and we'll finally be back to 2008 functionality! :)

  • PJTraill commented  ·   ·  Flag as inappropriate

    So it took 4 years, 2 months to put back a less integrated form of what should never have gone missing. I feel underwhelmed.

  • Roy Tinker commented  ·   ·  Flag as inappropriate

    In my opinion, a suitable macro language for Visual Studio would be:
    - Low-ceremony: a viable script could be written on a single line
    - Dynamic and interpreted
    - An otherwise powerful general-purpose programming language with powerful abstractions
    - Able to easily use .NET libraries
    - Fast

    What about Lua? I think lua scripting in Visual Studio would be a very exciting announcement.

  • George commented  ·   ·  Flag as inappropriate

    Totally agree with original post. Since macros were removed I ALWAYS install extension "Text Macros for Visual Studio".

  • Sagian commented  ·   ·  Flag as inappropriate

    Cathy Sullivan, please update the community as to when we can expect progress on this.

    Five months we've been waiting.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Yes.. The macros do not save all the actions. Lets imagine that I want to save a macro than includes searching for an specific word, substituting it, etc... If I save the macro and execute it it wont repeat the action to search the next instance of the word, just the typing.

  • SAM commented  ·   ·  Flag as inappropriate

    Macros aren't used often, but when you are creating or updating large volumes of code, they save HOURS and HOURS of tedious work.

    Please bring back as a built in feature!


  • Sagian commented  ·   ·  Flag as inappropriate

    It's been nearly four months since the survey and still no indication of intent. I'm pretty certain that 100% of the surveys want macros back and I'm also pretty sure that most of them would like to see it open-sourced.

    It's seeming more and more like the survey was a waste of time.

← Previous 1 3 4 5 33 34

Feedback and Knowledge Base