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.
I am still using VS2010 because of lack of macros!
Bring it back !!!
Skubi Dubi commented
I don't use Macros everyday, but when I need them, I NEED them... :)
Arnaud PAUL commented
The 1% of users that use this features is false.
Many dev uncheck the mark ""send anonymous usage statistics to help better MS products.".
It not because you don't see usage that mean that we don't use them..
Bring back the Macros please.
My producivity is 10% less that with an older version of Visual.
Record + Playback makes me 10x more productive. I've kept VS2012 only to be able to run macros, I'm usually in favor for removing cruft and seldom used features, but removing macros is CRAZY when other much simpler editors have it as a well supported feature. The scripting language should of course be Powershell, not VBA, not Python, maybe C#. You should have kept VBA until Powershell was integreated.
Michael Engshun commented
Not sure if the users were weighted (i.e., are the 1% writing a much larger percentage of code than the 99%)..
Regardless, almost ANY text-based editor needs a good macro feature set.
I used to copy other non .net files into studio when I needed to do complex text transformations. Please bring macros back
Ákos Tompos commented
I have created a couple of useful actions consisting of multiple moves (like copying the word under the cursor to clipboard) and assigned them to a single keypress. I want my speedy shortcuts back! Anyway %1 of Visual Studio user base is still a huge number! Just count how many licenses did you sell!
Jeff Relf commented
Microsoft should stop being so democratic.
The 1% who use macros write most of the best code.
Thanks to "Visual Commander", I've written extensions
for Visual Studio 2013 and I've assigned about 80 macros
to toolbar buttons and key strokes.
For the details, see: http://Jeff-Relf.Me/Macros.HTM
The scripting engine should have a preview option to make sure the script will do what you expect.
I would prefer the scripting language to be based on python. It should have complete control of the cursor as far as placement and text selection, and make it easy to replace/insert text as desired.
I mostly used macros for simple formatting changes.
Example macro keystrokes
[Home] -> [Ctrl-Shift-RightArrow x 2] -> [Delete] -> [End] -> [Ctrl-Shift-LeftArrow x 2] -> [Type Some New Code] -> [DownArrow]
If you could make that easy to write in your scripting engine consider me on board.
Alexey Shcherbachev commented
Please bring Macros back. I've been using macros for many text transformation tasks as well as some IDE related repetitive task, such as attach to a specific w3wp process running locally for debugging.
Eziquel Lima commented
I like macros, would not want it to be removed
Eziquel Lima commented
Bring back Macros
Keith Thorne commented
I had a number of macros for attaching to processes assigned to buttons, to debug all I had to do was click the button (or key). I have to do this over and over so what do I do now? I had also used them to plug gaps in features that eventually were made available but until then I had a way to automate. Please bring them back.
Igor Sapozhnikov commented
I tend to re-use some of the find and replace patterns. It would be nice to be able to save the Find and Replace dialog state for fast recall, or assign a keyboard shortcut to perform a specific find and replace operation quickly.
Simon Horridge commented
Why did you get rid of macros? not used very often, but very handy when you need to automate
i want it