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.
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?
Jeff Relf commented
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
I don't use the recording feature too often but I have used it in the past. However, I do use macros to speed up tasks that I link to keyboard shortcuts and which are otherwise to repetitive and lengthy done enough times every hour. Definitely want them back and will think twice before switching to VS2013, which we just did for one of our projects at work. This finding of no macros there is a very bad surprise.
George Celniker, VP Technology, SMS Inc. commented
We modify code on a large existing code pool that was created to a project design style. Amongst many uses, we use macros everyday to make consistent modifications to large numbers of files. It's a huge impact on my productivity to lose the macro record, edit, and playback features. Please bring this back. ASAP.
MS Lover commented
It makes you wonder what types of developers are on the VS team, if they think macros can be removed without any consideration.
Yet, Word has macros - wtf?
James Anderson commented
Never remove features, you never know who or when people use them. Macros often help with the little things that we don't want to have to suffer through...personally I want it so I don't have to go through "Attach to process"....then find the process to attach the debugger to the same process every time I need to debug the program.
Thanks for the consideration of reintroducing them, I hope that you bring them back soon.
We maintain multiple projects in a single solution, we created a macro to unload all project except for the target and it's reference to speed up our local build. Now we have to do all of this manually. Please return it.
99% of my usage was to record keystrokes and playback for repetitive tasks with search + cut/copy/paste. I hate not having at least that functionality
Les Smith commented
Macros had been a part of my code arsenal from the time they first appeared in VB and I continued to use them long after I switched to C#. I wrote several add-ins for commercial usage and was successful with it but I never stopped using Macros for code generation until they went away in 2012. For that reason and others, such as no real reason to upgrade, I still develop in 2010. I just completed a large Web Application in VS 2010. Those that say don't bring them back, IMHO never understood the real power of Macros.
Bishoy Botros commented
Not a smart step, VS team