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.
Since you ask, what I most want is the record/replay feature for temporary macros.
It occurs to me that you might be able to provide a quick but limited expansion of MSVS-programmability by allowing Tools.Customise to attach keystrokes not just to single IDE functions, but to sequences of functions and other keystrokes (both keystrokes to windows and to menus).
It would be a great help if you could do that in an update for MSVS 2013!
Anyone who ever tried to convert a table from the documentation into the code knows that macros are a must. I am amazed that no-one inside the VS team apparently uses these ...
WOW, No Macros in an IDE, Really?
That's really wired! such a powerful IDE like VS doesn't support macros!...
Aaaaaaaaaaaaaaaaaaaaarrrrrrrgh@#! I have just hit this too!
And I too am really annoyed (“Bastards” shot through my mind). I seldom use macros, but when I want them, it’s for a good reason.
Whether or not the 1% statistic is right, it is probably misleading. A (semi-)power user may record a macro that others find useful, or turn it into a VB function. People who care about this may be stronger advocates as well. And losing it just confirms that sinking feeling that you can’t trust MS to maintain a decent product without messing up the UI just as you had got used to it.
Incidentally, what I wanted to do was record a function to move up or down a level on the call stack without explicitly faffing around in the Call Stack Window.
All of you who continue to use VS 2010 should vote for this:
"Add .Net Framework v. 4.5 support to Visual Studio 2010"
Jeff Relf commented
My C# macros, to automate Visual Studio 2013
Astonishing! I just installed VS2013, and now have discovered to my horror that macros are gone.
I have used macros every day, many, many times during every development session. I've been building a macro library for over 10 years. What possible justification is there for removing automation in a *programmer's* tool like VS, while in Word, Excel and other Microsoft products the functionality is still going strong?
I have considered to purchase a private version of VS2013 because of the excellent XAML/WPF support, until I have discovered, that macros are not supported any more. With a VBA macro collection grown during the last 20 years, this is a NOGO. I really cannot believe this decision.
Please offer a VBA macro plugin as fast as possible. At least for making old VBA code running again and later on with a C# language support.
Florin DUMITRESCU commented
Every C++ developer I know is using them. Have used, actually. Temporary macro is a must.
Amazed this has gone, macros are extremely useful!
Having macros run when breakpoint hits is a powerful debugging tool. I've ran into situations that I need to set next statements a bunch of times for huge source code projects. This feature should come back!!
instead of wasting time thinking about api or whatever mess, allow simplest form of macro to format text. Better make it simple so it runs FAST and doesn't make it freez and choke when running macro. This way it will cover 95% of use cases and users will actually think that it was improved if macro starts to run as good as in notepad++
Chris Banks commented
We used macros to speed up the build massively. It would only build projects that depended on things that had changed and would stop on the first error. Saved us so much time. Please bring back macros or bake this in to VS.
Have you ever tried to use a code editor without keyboard macros? Bring back the macros - now!
Microsoft, could you at least provide me a method for attaching my debugger to a Windows service.
It was possible to do it with a macro!
Diana Canta commented
Huh, it is in review :). Tony Goodhew nice man ! Others that enter this vote also for Visual Basic 6.0 here: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi
Bring macros back.
You HAVE to be joking. Don't the Microsoft VS developers themselves use macros to save time?
Add to this the fact that the latest Windows update breaks macros in VS2008 as well.. Why not remove the ability to use a keyboard with it too?
There seems to be too much of a focus on adding features for stuff unrelated to actually writing any code.
Peter Grigg commented
I have used macros to save more than a few hundred hours of programming time over the last 8 years, not to mention just adding a date time stamp and name to the beginning of a comment which helps all developers know who made a change to the current line/section of a piece of code. Writing a small program to write programs is exactly what Macros are all about. From the responses that I've seen, it is clear that MS should not have eliminated this valuable tool and should work on restoring it to the product asap.