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.
Bring it back !!!
Maybe those 1% are your most productive users.
Actually, I only use macros for one thing: to replace a feature removed from yet another version of Visual Studio, namely the option to stop compìlation projects once one project has failed. If Microsoft had left that as an option, I wouldn't need to resort to macros.
Of all the user bases, surely developers are least likely to respond to well to this "Daddy knows best" attitude?
Phil Rogers commented
No macros? Less than 1% use them? Well if nobody used them, that's ok, but I'm sure 1% is still a significant number. And those who use them probably use them a lot. Maybe the other 99% simply don't know about them.
They worked, so why drop them? Leave them in for us enlightened few.
Michael Rubinstein commented
What were you thinking? I'm just switching from 2010 to 2015. I can, sort of, understand that you left it out in 2012. But I'm amazed that you haven't put it back in yet. Don't you folks write any code?
RE: MarkieMacro commented · April 21, 2015 5:33 AM
¿Surely you can use Tools–Customise–Keyboard for a shortcut to show/hide line numbers?
Macros are needed when your commands include (specific cases of) variable arguments.
I want to add a keyboard shortcut for show/hide line numbers... I need a macro for this =(
James Curran commented
What 'd really like (instead of or in addition to a proper macro language), is a simple FAST keystroke recorder.
I'm assume that you dropped the macro feature because your telemetrics found that no one was using it, which I'll assume is because everyone realized what I did ---- when I needed a keystroke recording/playback, it was much, much faster to copy'n'paste the whole file in NotePad++, do the task there, and then copy the file back into VS
armen keshishian commented
Please bring it back, I don't know how what was the reason behind that, I red in some blog that only 1% of developers are using it, who did that investigation? no one asked me! ;) In almost every job that I had more than 75% of devs were using it and even more, enjoying it. So please bring it back.
Please, bring it back, we're losing too much time without macros... Microsoft have a macro system on near every product, visual studio is a programming software, put macro on it...
Please bring it back, it is a pain to work without them and a consistent loss of time
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!