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.
Richard Broadhurst commented
Was the 1% figure from vs2010 professional+ or does it include all those on express who didn't even have macros?
Raymond Yang commented
Macro gives us valuable help to discover and learn Visual Studio API. If it is disappear, we have to put more time to read document and search samples to accomplish our work. I knew macro is dropped out from Office, why it dropped from Visual Studio, too? Please bring it back!!!
Jim Nickerson commented
Please bring back macros
Lonnie McCullough commented
I cannot believe you cut Macros. The feature seemed to work well enough in VS 2010. This is a huge step back. I do all kinds of repetitive work with Macros and you've essentially made the kind of work all professional devs must do 10X ****** (even if it was only 1% of us). Was the VS team seriously OK with cutting this feature? Aren't you guys devs first?? Maybe the reason temp macro recording doesn't show up in your usage breakdown is because you made the feature so easy to use that no one had to spend much time worrying about it....until it was gone.
Bring back macros
What a waste of time! I could have done int in 5' with a macro.
I do not understand how MSDN (=Visual Studio) price dares increasing while its functionalities are removed : M$ go to jail, don't pass go, don't receive $200!
found my way here after googling where are macros in visual studio 2012. I would like macros returned.
David Johnson commented
I never used it in previous versions, but now I've gone looking for it in VS2012 only to find that it has been removed. Please put macros back.
Jeff Relf commented
My Visual C++ code automates Visual Studio and Excel
using the OLE version of VBA scripts.
In Visual Studio, I hit F7 and start recording craρ.
When done, I hit F7 again. To play it, I hit F8.
If I want, I can edit the recording ( i.e. the VBA script ).
Also, I write VBA scripts ( a.k.a. "macros" ) by hand; to wit:
These "Sub" routines are assigned to keystrokes
and toolbar "buttons"✼. Some of them launch apps I wrote,
including apps that automate other apps.
[ ✼: http://Jeff-Relf.Me/Visual-Studio-2010-Toolbars.PNG ]
I've been using "Macros" ever since 1983;
no way in hеll would I stop now, just because Microsoft
claims Visual Studio 2012 is an "upgrade" ( it isn't ).
Forget BACKWATER emacs, forget "Rad Studio"...
Microsoft can't compete with its prior self.
Microsoft has lost talent, it can't maintain its code.
While I prefer Windows 8, many SMART people prefer Windows XP.
I use Office 2007 and see no reason to "upgrade".
Sometimes I opened the VS just because the macro util to do some text editing stuff :)
Leon Ball commented
Maros were an absolutely invaluable tool. The ‘improved’ pending changes window is clumsy. VS2012 stincks.
Mike Nakis commented
If I knew there are no macros in VS2012 I would have saved myself the trouble of upgrading from Windows XP to Windows 7 and reinstalling all my stuff from scratch. The all caps menu is fixable; the awful colors are fixable; the dreadful icons I can live with; the rest of the god-awful ugliness I can live with; but the macros? I cannot work without macros! So, I am reverting to VS2010 and sticking to it for now.
I just started using vs2012 and so far I can't find anything I like better than 2010. Now I find out I'm losing macros I've had for years? Please revisit that decision.
Macros were not a daily use item, but were INVALUABLE when I did use them for bulk reformatting and data extraction. Consider that I cannot post "anonymous usage statistics" from my employers computers. I imagine many professionals are similarly security encumbered, so your usage statistics are probably not representative. Bring 'em back and quick. I'd really rather not switch IDEs but if you can't maintain world class features (like ones you've had for a decade!) then you're not really in the game.
John Cronan commented
A product whose only purpose is to write code, that doesn't support macros? Wow! Hard to believe.
I can not think of a single respect in which VS2012 is better than VS2010. I won't recommend that any of my projects move to it. Ever. I can only hope the hue and cry will properly motivate Microsoft to fix its many problems in the next version.
Paul Howarth commented
I'm using the Pro version... It looks like a tacky mobile app, the black and white icons are a complete joke (unless you are using a grey scale monitor I guess). The removal of the record macro is also a pain. A complete downgrade from 2010 as far as I am concerned.
Stanley Morris commented
Visual Studio dev since v1.0. I use macros every 1-2 weeks. There is no such thing as a good editor without macro recording. Was this choice made by the same enlightened team that decided that I should use a tablet interface for my workstation?
Jeff Elliott commented
Another vote for macros. I'm crippled without them!
Just enable them in Prof/ Ultimate Versions only.
Experiences developers use experienced features
I can see how Microsoft might want to move FORWARD from COM era VBA to something new and shiny (heck, I'd take VBA with .NET Framework access).
For ME, the point is that the small macros I built do not justify the effort of building an extension. Developers need a "middle road" for custom behavior.
I also question the "1%" assertion by Microsoft. "1%" seems like more of a straw man to me. In any event, if I build macros, then surely the REAL dedicated developers must have more and bigger macros that they depend on.
Is this the "1%" that Microsoft wants to anger?
Richard Broadhurst commented
Is this 1% all vs users including express who couldn't use them anyway, or the "professional" users that seem to be the most common ones here?
Michael Sneen commented
I agree completely!