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 would like to execute a macro after I press F5. IE:
Enter username/password in a LoginForm
A messageForm displays.
Press the Ok Button.
The MainMenu Form displays.
Change the value of a ComboBox
Click on an item in a ListView Control
This wil load the form i'm currently working on and stop the debuuger on a breakpoint.
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.
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.
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...
Removing temporary macros is another example of Microsoft arrogance.
Bring back macros, or something similiar
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 Davis commented
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.
WTF... doesn't anyone in Microsoft use macros?
What IDE are you guys using?
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?
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!
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 ...
WOW, No Macros in an IDE, Really?
That's really wired! such a powerful IDE like VS doesn't support macros!...
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.
All of you who continue to use VS 2010 should vote for this:
"Add .Net Framework v. 4.5 support to Visual Studio 2010"
Jeff Relf commented
My C# macros, to automate Visual Studio 2013
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?
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.
Florin DUMITRESCU commented
Every C++ developer I know is using them. Have used, actually. Temporary macro is a must.
Amazed this has gone, macros are extremely useful!
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!!