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.
I heard only 1% of folks use this feature therefore it was cut from VS 2012. I really need a way to automate things inside the IDE such as creating files. Writing an extension to do this is way too much work. It would take a very long time to payback the dev hours needed to code up an extension. Keep in mind that 1% is only the 1% of folks that chose to opt into having their usage tracked.
Last week I tried to use Macros and I noticed that feature was cutted out from VS11 Beta. So I have to do it through Notepad++ and finally copy the code into VS11.
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.
I am astonished as I cannot use my ten-years-old macros I have used during my life as a developer. Please, bring back macros in visual studio. It is just the same extension, it is not necesary to remove it. Thanks.
Christina Schelin commented
Please at least release the source code, yes. Just because not everybody uses a thing doesn't make the thing unuseful.
I use macro record/replay every day in VS2010 and I can't imagine being without it because it saves me so much time. I also have a library of macros for often repeated tasks. I can't believe MS have dropped these incredibly powerful features, hope they bring them back in future. Looks like I'm staying with VS2010!
Douglas Holt commented
I use any one of dozens of macros I've written over the years every few minutes!!! I don't know a single developer that doesn't rely heavily on macros! WTF are you thinking by removing them???
BRING BACK MACROS!!!
Why take macros out?
Its like BMW removing the rear view mirror on the new series 3 GT, because their drivers don't use them enough.
I need macros! Most of my project use the macro for some auto works, GET it Back pls!
John Gietzen commented
They would be used more if they could be developed in a C# REPL.
Also, things like repetitive one-off tasks would benefit from such a repl.
The only reason why I purchase the paid version of VS is for the macro facility. I've written about 30 macros over the past several years, and I cannot live without them. I've been doing things with macros that I've never seen anyone else do, and they're hugely valuable to me. I've been entertaining the idea of bundling up my macros and selling them - I believe that a lot of you would pay me good money to use my macros (and the system that it supports).
I absolutely WILL NOT "upgrade" to 2012 for this very reason.
I am shocked and stunned that it's been dropped.
BRING BACK THE MACS!!!
Alfonso J. Ramos commented
Microsoft has already said they removed macros because maintaining them as like having to maintain two IDEs. I think a version of Visual Studio without macros was needed as an improvement and help the IDE evolve. Now, after that was done, it think it is time to find a way to use the new and improved IDE to be able to make macros for itself.
By the way, the provided work-around is to make extensions for the IDE. I have never had the patience for writing a proper extension to solve a problem, because I can solve those problems "the old way" faster.
In fact, that is why it has been said that what people want is record and play. I - for intance - would start by recording a macro of me solving the problem "the old way". Yet, I won't use third party macro solutions - as suggested by many - because I cannot extend those. That's right, after recording I would go to edit the code and add logic to it, extra checking that I could not possible record because happened in my mind, and maybe some UI.
Tim Phoenix commented
When I received my new workstation from corporate IT with VS 2012 installed, I was elated.
I have my own VS Pro and MSDN license for personal use, but had not yet "upgraded" to 2012 at home. I was hoping for big improvements as I was underwhelmed by some of the "improvements" in VS 2010.
The VERY FIRST order of business was to import my macros. You know, the macros I've been using and extending since VS 6, the macros I use dozens of times per day, every day.
I couldn't find where this option was now located in the ugly 2012 UI, so I googled it.
I can't even begin convey my astonishment and my outrage to find that macro support has been removed!
Now that my anger has subsided a bit, I find this just laughable. How stupid must one now be to make decisions at Microsoft?
I've grown very cynical about Microsoft in the last few years. Valuable components and options were changed and/or removed in Vista and again in Windows 7. Windows 7 was unusable for me until I found and installed several 3rd party utilities to fix some of Microsoft's blunders.
IMO, above all of the other bad decisions made by Microsoft, and there are many, removing macros from Visual Studio ranks as the worst. I personally feel that they gave all of us developers a great big middle finger.
Mike Nakis - I totally agree with you on this: "if that's all you care for [record/play], then please do yourself (and all of us here) a favor".
Mike Nakis commented
Many people mention that most of their interest in macros lies in the record/play feature.
People, if that's all you care for, then please do yourself (and all of us here) a favor and go get a third party macro solution, like macroit, and be done with it.
The real value of built-in visual studio macros lies in the actual integration with visual studio, that is, in being able to control the editor and the development environment with the macro language. The ability to actually record the macro and assign it to a key is just a nice thing to have on top of the core functionality. If you have never done that kind of stuff, you have barely scratched the surface of the possibilities offered by visual studio macros.
Why remove a working feature!?!? I've used it since 2001! Please bring back at least the record/play feature.
Ari Johannesson commented
I often use macros. Want them back.
I also suggest macros is possible in VS2012.
If not advanced macro development, then at least the record/play functionallity.
But implement that its possible to play shortcut-functions too, then you have a winner.
In fact, I think thats what many developers avoid using macros - because of the limitations, not because they're useless.
I have loved this feature since 1995....
And I just can't believe they would take it out of VS...
Jeff Relf commented
I use macros ( i.e. VBA scripts ) hundreds of times per day.
Several "buttons" in my ＜toolbars＞[✼] launch ＜macros＞[✼✼],
as do many of my 39 mouse⋅buttons ( http://Jeff-Relf.Me/G600.JPG ).
Back in 1993, with Developer Studio ( c ),
I vividly recall how dаmn ＳＬＯＷ macros were.
To this day, they're ＤＡＭＮ ＦＵＣＫＩＮＧ ＳＬＯＷ.
Still, I wouldn't, couldn't, live without them.
So long as Visual Stuidio 2010 remains the best option,
I'll stick with that, no need to "upgrade" to VS2012.
+1 here. Simple code editing tasks that I could automate through record/play are almost impossible now.
I hae 1000+ lines where I need to add ") at the end of line. Thank you Microsoft for having to do that now manually. I'll send you my doctor's bill...
Macros are one my favorites, and it can saves a lot of time during development. It was really a shock when I find out it has been removed.
Saddened Developer commented
Please bring macros back. I can't believe you've removed such a useful tool!