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.
We’ve heard your feedback loud and clear, and we’ve been working on a solution. We’re therefore very happy to announce that we’ve now released a version of Macros that supports both Visual Studio 2015 and Visual Studio 2013.
While we were at it, we took the opportunity to fix a couple of bugs and improved the keyboard shortcuts.
We hope you enjoy it.
For more information, see the blog post here: http://aka.ms/vsmacros
We’ve also open-sourced the code under the MIT license. If you have any suggestions or contributions, feel free to create an issue or a pull request in the new GitHub repo: http://github.com/Microsoft/VS-Macros
Senior Program Manager
Visual Studio Extensibility Team
I want my Macros!!!! Please
Jeff Waskiewicz commented
I want my Macros!!!! Please
Jeff Relf commented
For me, Vlasov's Visual Commander solves the "missing macros" problem.
Please! I need a way for my team to perform resharper code cleanup on file save.
PLEASE, PLEASE bring them back. I used them constantly.
We were using .vsmacros/.vsmproj a lot to automate different tasks on files in our sources. VBA is terrible to make macros but result functionality was perfect!!! Dream about get it back!
Until macros are coming back I will always have a VS2010 version in parallel. Bring them back!!!
Macros were invaluable. Record/playback and simple automation were extremely useful. I believe that average developers were not aware of their existence, otherwise macros would show much better usage statistics.
Alan Bates commented
I don't understand why the feature was just completely dropped. An adamant but small-ish developer community with disproportionate support costs borne by the vendor? The macro IDE seems like it was a perfect candidate to be tossed to codeplex.
I understand that there was a large maintenance cost for updating the IDE to work with each new VS flagship release...but couldn't it have alternatively been declared an End of Life product, Visual Studio would maintain the capabiliy to run generated macros, but the validity of those macros would no longer be validated by the Visual Studio team?
...mad that they're gone (I hated writing them in VB but you could create a lot of useful, private, ad hoc extensions with them) but hopeful that they'll be back.
Marc-Antoine Proulx commented
Please bring the Macros back. I just don't understand how somebody came to the conclusion that they needed to be removed. I don't use them that often, but it's very useful when I do.
Please bring Macros back in VS2013. Just for simple text editing would be sufficient for me.
Mr. Bush commented
PLEASE bring back Macros!! I used the constantly.
I use them often. Please bring them back. Every thing else about this IDE blows the competition out of the water. Give me my macros back!
I want them back! I used to use them all the time.
Howard Berg commented
LightSwitch is rapidly becoming mature, but in the meantime, I prefer to automate creating/updating screens (e.g. loop for each table/screen) vs one at a time. Like always, I would use a macro to learn the API calls required to do a task, and then write the macro to do the work.
Macro has alwas been an extremly useful and powerful text-editing feature, I wonder who ad whay had the idea to remove them ? I want to have it back !
Horrified to see that macros were gone! I used it almost every day... Luckily, some guy on the web provided an extension... but hopefully, MS will bring this one back.
I just cannot understand what MS was thinking about... Too bad too many frustrated programmers won't see this link here, to express their own frustrations...
Just upgraded from VS2008 to VS2013. Missing at least two features:
- Macros were used daily.
- Find Symbol.
Definitely need them back.
Jim Nichols commented
Macros were a huge part of my development process. The ability to not only record a macro but create a toolbar button for it aided me EVERY DAY!!!! Macros should be just as much of a part of Visual Studio as they are in Office.
I've read that Microsoft removed Macros from Visual Studio, because their statistics showed that it was not an oft used feature. I can tell you, I did not use it often myself, but when I did find a need for it, it made a HUGE impact and cut my work load down by many times.
Because a feature is not often used does not equate to its importance.