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,415 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  ·   · 

    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.

    595 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...
      • MS LoverMS Lover commented  ·   ·  Flag as inappropriate

        It makes you wonder what types of developers are on the VS team, if they think macros can be removed without any consideration.

        Yet, Word has macros - wtf?

      • James AndersonJames Anderson commented  ·   ·  Flag as inappropriate

        Never remove features, you never know who or when people use them. Macros often help with the little things that we don't want to have to suffer through...personally I want it so I don't have to go through "Attach to process"....then find the process to attach the debugger to the same process every time I need to debug the program.

        Thanks for the consideration of reintroducing them, I hope that you bring them back soon.

      • Anonymous commented  ·   ·  Flag as inappropriate

        We maintain multiple projects in a single solution, we created a macro to unload all project except for the target and it's reference to speed up our local build. Now we have to do all of this manually. Please return it.

      • Anonymous commented  ·   ·  Flag as inappropriate

        99% of my usage was to record keystrokes and playback for repetitive tasks with search + cut/copy/paste. I hate not having at least that functionality

      • Les SmithLes Smith commented  ·   ·  Flag as inappropriate

        Macros had been a part of my code arsenal from the time they first appeared in VB and I continued to use them long after I switched to C#. I wrote several add-ins for commercial usage and was successful with it but I never stopped using Macros for code generation until they went away in 2012. For that reason and others, such as no real reason to upgrade, I still develop in 2010. I just completed a large Web Application in VS 2010. Those that say don't bring them back, IMHO never understood the real power of Macros.

      • CHJCHJ commented  ·   ·  Flag as inappropriate

        You need to bring this feature back or offer some good alternatives. Can't leave people hanging like that.

      • Anonymous CowardAnonymous Coward commented  ·   ·  Flag as inappropriate

        Whatever executive decided that Visual Studio macros weren't used and that Visual Studio extensions are a perfectly fine substitute needs to be fired.

        Don't worry! That person will be quickly hired, fit right in, and have a long, happy career at Initech or Veridian Dynamics or Uranus Corporation or working with the pointy-haired boss.

      • BrianBrian commented  ·   ·  Flag as inappropriate

        I use keystroke record/playback too often to give it up. There's nothing better for repetitive tasks. If I can find a decent free editor with record/playback, I may upgrade to later VS and use the 2nd editor when needed. More likely, I'll just continue using VS2010 until you restore simple key record/playback.

        By the way, VS2010 introduced an subtle bug in record/playback. It doesn't handle "home" keys right or something similar. The result is that I always had to work around the issue with different key techniques. Still far better than no record/playback!

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        Don't do it in a future version - give us an add-in!
        I should have stayed with VS2010 the upgrade to 2013 came with no macros, all my setup projects are now incompatible and regtlbv12 is gone what other improvements can I expect?

      • shimmyshimmy commented  ·   ·  Flag as inappropriate

        If not macros, at least an appropriate way to make up commands by script or other way, but there has to be a way to do some automation.

      • Christian LafranceChristian Lafrance commented  ·   ·  Flag as inappropriate

        What the **** is this thing of removing macro support in VS2012/2013??? Yes, the IDE does already alot, but not all and especially those specific things that can make ME save so much time. Thanks for bringing it back!!!

      • samsam commented  ·   ·  Flag as inappropriate

        I use the simple record/playback ALL the time and would love to see the feature return. If not that, allow an option to open the code up into Notepad++

      • Glauco BasilioGlauco Basilio commented  ·   ·  Flag as inappropriate

        I used to use macros combined with custom shortcuts to turn my envoriment more "keyboard" friendly, once i suffer of mouse pain. Now my macros became obsoletes

      • GeorgeGeorge commented  ·   ·  Flag as inappropriate

        I use it often for some comments editing, and found it inefficiency to do it with VS2013.

      1 2 5 7 9 29 30

      Feedback and Knowledge Base