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

    567 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...
      • BillBill commented  ·   ·  Flag as inappropriate

        Oh My, just started with 2013 from 2010 and no macros. I guess your coders don't do a lot of repetitive tasks or they would know the value of them. I always thought 2010 was slow with recording and playing back macros but I lived with it. Not fun jumping out of vs to do macro processing and then jumping back.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Really unbelievable, that VS lacks macros. I used them often, for every recurring action. Is really no MS programmer missing them? How do they edit code? Without a macro recorder?? Unbelievable...

      • Anonymous commented  ·   ·  Flag as inappropriate

        I may be the only person who uses macros, but i use them every minute of my day. I used them for absolutely everything. If there are more then 2 lines of code where i have to make similar change, i use macros... who the **** decided to remove macros? This is the only feature that I use from this ******** IDE... Everything else came from plugins such as Resharper. Did you actually think that replacing macros with black background is funny? this is a joke i cant believe i gave Microsoft about 15 years of my life. I am moving to Linux now (long overdue)...

      • Pete DavisPete Davis commented  ·   ·  Flag as inappropriate

        I don't use them often, but occasionally they're very valuable! What's frustrating is that were they implemented a little better (in a more accessible, easy to use way), I think they would be more useful. I think the biggest problem with them is that they're just a pain to use the way they've been implemented in the past.

      • JenJen commented  ·   ·  Flag as inappropriate

        WTF... doesn't anyone in Microsoft use macros?

        Seriously?

        What IDE are you guys using?

      • Anonymous commented  ·   ·  Flag as inappropriate

        Among many irrational decisions in visual studio product, this is unbelievably irrational. How could an IDE not have any scripting capability? What were you thinking?

      • PJTraillPJTraill commented  ·   ·  Flag as inappropriate

        Since you ask, what I most want is the record/replay feature for temporary macros.

        It occurs to me that you might be able to provide a quick but limited expansion of MSVS-programmability by allowing Tools.Customise to attach keystrokes not just to single IDE functions, but to sequences of functions and other keystrokes (both keystrokes to windows and to menus).

        It would be a great help if you could do that in an update for MSVS 2013!

      • DimaDima commented  ·   ·  Flag as inappropriate

        Anyone who ever tried to convert a table from the documentation into the code knows that macros are a must. I am amazed that no-one inside the VS team apparently uses these ...

      • HessamHessam commented  ·   ·  Flag as inappropriate

        That's really wired! such a powerful IDE like VS doesn't support macros!...

      • PJTraillPJTraill commented  ·   ·  Flag as inappropriate

        Aaaaaaaaaaaaaaaaaaaaarrrrrrrgh@#! I have just hit this too!
        And I too am really annoyed (“Bastards” shot through my mind). I seldom use macros, but when I want them, it’s for a good reason.

        Whether or not the 1% statistic is right, it is probably misleading. A (semi-)power user may record a macro that others find useful, or turn it into a VB function. People who care about this may be stronger advocates as well. And losing it just confirms that sinking feeling that you can’t trust MS to maintain a decent product without messing up the UI just as you had got used to it.

        Incidentally, what I wanted to do was record a function to move up or down a level on the call stack without explicitly faffing around in the Call Stack Window.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Astonishing! I just installed VS2013, and now have discovered to my horror that macros are gone.

        I have used macros every day, many, many times during every development session. I've been building a macro library for over 10 years. What possible justification is there for removing automation in a *programmer's* tool like VS, while in Word, Excel and other Microsoft products the functionality is still going strong?

      • RainerRainer commented  ·   ·  Flag as inappropriate

        I have considered to purchase a private version of VS2013 because of the excellent XAML/WPF support, until I have discovered, that macros are not supported any more. With a VBA macro collection grown during the last 20 years, this is a NOGO. I really cannot believe this decision.

        Please offer a VBA macro plugin as fast as possible. At least for making old VBA code running again and later on with a C# language support.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Having macros run when breakpoint hits is a powerful debugging tool. I've ran into situations that I need to set next statements a bunch of times for huge source code projects. This feature should come back!!

      1 2 5 7 9 28 29

      Feedback and Knowledge Base