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.
Even if only 1% (I highly doubt it) users are using a feature, still that translates to hundred of thousands of programmers. How can you ignore that many programmers.
Doug Kent commented
I can`t imagine any professional developer not using the macros feature.
Andrew Myers commented
For Web Development creating a macro to attach to w3wp.exe with a key stroke is very useful. Sure I only code a macro every once in a while, but once it is created I use that macro often. I was surprised that macro's were removed from VS 2013. I just upgraded from VS 2010.
Unlike MicroSoft, sane developers know
that intelligent comments, from users,
matters most, not "usage statistics".
You rock, Jonathan !
For once, I made it to
■ · the top 1% · ■
For once I am the 1%
Eugenijus Drabuzinskas commented
Cannot believe my eyes - someone states that macros were use by 1% or VS users. But I feel this 1% is most advanced and most valuable of all VS users.
Please bring this feature back!
Macros are very useful in some debugging scenarions especially in relation with breakpoints. It's unbelievable that the vs team doesn't realize these benefits.
Most macros I used were navigating on the error list -- exporting text to other editor is not a workaround
Why remove Macros ? It's REALLY useful for me to edit existing code.
Dave Apelt commented
I know it is infrequently used, but when it is needed, it will save your day. Please bring it back.
Macros are essential for some quick text, source code and XML editing activities. Although I don't use the feature every day, I actually depend on it for certain things. So I might have not turned on the "share information with Microsoft" like many others - in that context I wonder how reliable it is to base decisions on "blind statistical data". In my opinion it is the richness of text editor that was a big part of making Visual Studio so successful. Why throw richness away making people consider other text editors for some tasks and annoying this "less than 1%" of users, many of whom are likely the decision makers and could count as 1 for 10 in a vote?
For me, Sergey Vlasov ( in Chelyabinsk, Russia ),
has solved this problem ( automating VS·2013 ).
Sudarsan Srinivasan commented
Need macros. I cannot copy paste my code to Notepad++ just to record and run a macro!
Troy Hughes commented
Please bring back macros!
Honestly, how much effort would it really have been to continue supporting scripting?
One day, these types of decisions will come back to bite you. You chose to slightly reduce your workload by increasing the workload of everybody that uses your product.
Mihai Dobrescu commented
bring back macros - cleaning code is a nightmare without them...
David Guo commented
Bring it back!!!!!
Please bring back macros! The VS macro tools have been a huge benefit to my productivity, and saved me and my team countless hours of typing repetitive code segments.
Robert Wilingakar commented
I have to open my project's .cpp and .h files in VS2010 with enough project settings as to be able to use intellisense, use the macro there, and copy the .cpp and .h files back in VS2012. Fortunately for me, my codes still are recognizable in VS2010. To be honest this is a bummer