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 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 ! now! realease a hotfix to solve this issue!!
What a shame!!!
SHAME, SHAME, SHAME!!!
Bring it back!!
Atis Straujums commented
I typically don't use macros proper (writing them, using the API and such) but I often use the quick recorder to record key strokes, sometimes in a rather sophisticated way, and it was one of the features that distinguished VS from, say, Eclipse. Please keep at least the recording/playback feature -- I would not care about editing.
For me, ＜Sergey Vlasov's Visual Commander, Professional Edition＞[*]
solves the "missing macros" problem.
[ *: http://vlasovstudio.com/visual-commander/professional_edition.html ]
It lets me assign up to 99 macros to keys/buttons[*];
without that, I simply could -not- use Visual Studio 2013.
[ *: My assignments:
After making changes to my hand⋅crafted macros ( Snippets.TXT ),
I copy it to the file that Visual Commander uses:
C:\__\AppData\Sergey Vlasov\Visual Commander\1.0\Snippets.vCmd
My "Open File" macros are in a "New Menu", on my toolbar.
"File > Recent Files List" fills a similar "New Menu". ]
Also, Visual Commander comes with a super⋅nice/essential,
"Hide the 'Sign in' and 'Feedback' buttons" extension.
The macro editor uses the standard text/code editor;
so you get ＜the fonts you want＞[*], properly colored/sized[**].
[ *: I use Apple's "Menlo" font, Microsoft's "MS Mincho" font.
Menlo has the best '0' glyph, see: http://Jeff-Relf.Me/X.PNG
**: For me, C# macros ( .CS files ) are C++ colorized ]
Unlike VS⋅2010, the Macro editor is a tab, not an app;
so debugging macros is a real joy.
For me, F7 starts/stops recording, F8 plays it.
The macro recorder has many faults; but recording isn't essential.
FYI, This toggles "ShowHorizontalScrollBar" On/Off:
= DTE.get_Properties( "TextEditor", "C/C++" )
hScroll.Value = !(bool)hScroll.Value ;
1.) This no longer works properly[*]:
[ *: it changes your find⋅history/find⋅settings ]
By the way, I put "not found" messages
in the ＜StatusBar＞, like this:
DTE.StatusBar.Text = @" Not a ■⏎⏎■⏎ file." ;
2.) This no longer works properly[*]:
[ *: these tabs aren't updated when changed outside the editor ]
Use: DTE.ExecuteCommand("File.OpenFile", "C:/__/X.TXT");
3.) This no longer works properly[*]:
[ *: modified tabs aren't updated ]
sergey logunov commented
I have used VS for about 20 years (starting from MS C++ 2.0) and record-play macros almost every day. The first thing I looked for after VS1013 installation were macros
Err that's a bit harsh, Jim don't scare off the PMs! But seriously, wasn't Visual Studio macros supposed to be a showcase for the VSTA debugger/IDE that developers can license? (See here: http://en.wikipedia.org/wiki/Visual_Studio_Tools_for_Applications ) Personally I thought this was a really cool offering, but the unrealistic $50 per-seat license totally killed it, especially alongside free alternatives like SharpDevelop, Python, LUA, etc. If Microsoft offered a reasonable royalty-free developer license that could be purchased without being hassled by a sales guy, I bet VSTA would be really successful. And then maybe Visual Studio macros would get more love. Just sayin', there's more options than ditching macros entirely. Big apps like SolidWorks and ArcGIS licensed VBA despite all its terribleness, so there is a market need here.
Jim Fannigan commented
This is apparently the decade of Microsoft making stupid decisions, ignoring the voice of reason, and then finally listening to customers in an embarrassing reversal. Examples: no start button or boot-to-desktop for Win8, no early access for Windows 8.1, limiting Windows accounts to five devices, the whole XBox One DRM thing, preventing indie game developers from selling games in the marketplace... the reversals just keep rolling. It's great that customer needs are ultimately being met, but Tony Goodhew, how hard is it to listen to a customer once in a while and avoid these problems? Other companies seem to be able to do that.
David Jade commented
I cannot believe you removed macros. I use them all the time for automating editing, mostly by recording keystrokes. This is such a core function for me that I often use VS as my editor of choice when I have to munge complex data files.
BP in NC commented
Wow. For me macros are one of the most useful features in VS. I can't believe MS took it out. Definitely a vote from me to either bring it back or make it open source to the community can maintain it.
A cardinal rule I learned many, many years ago working as an ISV is that you never take features away on an upgrade. For me, the least capability you should offer is to put it back the way it was.
Lloyd Franklin commented
I've made the move from 2010 to 2013 after much consideration to the premium cost and no upgrade path from previous versions.
My first impressions with 2013 have been good so far, but when I looked to set up my macro project and get some work done - total shock and disbelief - a real blocker for me.
I don't understand Microsoft anymore. I used to feel so confident choosing your tools. I thought the 'Start menu' removal and its limited reintroduction in 8.1 were baffling - but this surpasses even that for me.
I'll check out the 3rd party alternatives, just like I had to with the Start menu. But it's a negative experience for me.
I'm less interested in the full 'vs.net scripting' than I am on the ability to record and playback the keystroke macro. CTRL-SHIFT-R was my goto for doing tedious **** and now its gone. Bring it back!!!!
Jason Brown commented
I pressed SHIFT-CTRL-R and started editing - and nothing happened. After a little hunting around for the macro toolbar I Googled it and came to this page. I have to say I'm absolutely gob-smacked that macros have been removed. Why not remove copy and paste next - or perhaps the ability to type the letter Z - that's not used much.
Crazy! Come on - put it back in...
I use macros heavily, albeit not every day. Mostly for repetitive tasks where a T4 template is overkill, and regular expressions in the Find/Replace dialogs just doesn't give me what I need. Please bring macros back.
Matthew Newhook commented
I cannot believe you remove macros from VS2013. I used temporary macros continually in my workflow. Now what? I have to copy & paste my code into some other text editor when I want to do something more complex? What kind of upgrade removes incredibly useful features! Bring them back ASAP.
I use it in ways that simple text replacement wouldn't work.
- Add sibling folder. Having to scroll up to the parent folder. Actually if you just improved the tree control to have a context-clickable breadcrumb to show where you currently are at the top of the tree, this would probably solve this and other problems I have with large projects.
-- Add text to the top and bottom of my ssdt sql script which includes
-- getting the filename of the current file
-- calculating the number of padding characters required considering the length of the current filename and adding them in
-- adding in a guid to ensure uniqueness
- Trying to work around other deficiencies in the SSDT system that haven't and won't be fixed based on my Connect requests. Such as providing a keyboard shortcut to change the current database in a ssdt non-build script.
It seems to me that one can't have it both ways, either fix and improve the existing tools (i.e act on reasonable connect feature smoothing requests) and commit enough resources to do it or provide an alternative for us to fix it ourselves. If you do neither people will start looking elsewhere and perhaps find cheaper alternatives. You have to keep VS to be the premium feature-rich product and removing these kinds of things is a clear mistake.
Macro's and centralised commands was one of the stand-out features that other IDE's missed. I am amazed and dismayed that this decision was taken.
Suppose you use Visual Studio 2010 ( not Visual Studio 2013 ).
Suppose you want to hit a key and/or Toolbar⋅Button,
and/or mouse button ( if you have ＜my logitech g600 mouse setup＞[*] )
[ *: http://Jeff-Relf.Me/g600.JPG http://Jeff-Relf.Me/g600.TXT ]
to manually delete a large "block of lines" ( BoLs ),
from a long list of BoLs, "^ ■$" separated ( RegEx ), like this: ＜＜
Wizard-Of-Oz│somewhere＠over⋅, Androcles⋅, hanson│hanson＠quickΞnet
jimp＠specsol⋅spam⋅suxΞcom, tre⋅Bert, Ben⋅Jacoby, bilgat＠mΞnu
Gecko( May⋅2013, Mozilla, Mar⋅2013, Oct⋅2012, Sep⋅2013,
Nov⋅2012, Jan⋅2010, Jul⋅2012, Aug⋅2013, Jun⋅2013, Mar⋅2012, Jun⋅2012 )
Google⋅Groups, Outlook, F⋅Agent, Xnews, Live⋅Mail( Windows )
tin( Sun, Linux ), Pluto/3⋅04c, Pan, Xpress, Win⋅Mail, operaMail( Win32 )
NewsWatcher( Mac ), NewsTap( iPhone ), X.HTM, MicroPlanet, nn, ⋅
XanaNews, xrn, NewsFleX( Linux ), trn, Pine, 12:29:57, Postbox⋅3⋅0⋅8
MS⋅Entourage( Mac ), KNode, slrn( Linux ), WinVN, Emacs, Thoth( Mac )
MacSOUP( Mac ), MesNews
GigaNews( Megapath⋅NET, Giganews⋅COM, Saix⋅NET, Omsoft⋅COM,
Btinternet⋅COM, Brightview⋅CO⋅UK, Earthlink⋅COM )
High⋅Winds( Teranews⋅COM, Virginmedia⋅COM, Newshosting⋅COM, Sjrb⋅CA )
Alt⋅NET, Atman⋅PL, Individual⋅NET, Sub⋅DE, Netfront⋅NET, Bnb-LP⋅COM
Newsguy⋅COM, Albasani⋅NET, Astraweb⋅COM, Telekom⋅AT, Glorb⋅COM
Synserver⋅DE( Synergetic⋅AG ), TheWorld⋅COM, Supernews⋅COM
Readnews⋅COM( Usenet-News⋅NET, Usenetmonster⋅COM, Iglou⋅COM )
Mixmin⋅NET, Twtelecom⋅NET, Panix⋅COM, Kpn⋅NL, ED⋅AC⋅UK, Tut⋅FI
Cornell⋅EDU, Easynews⋅COM, HP⋅COM, Cmu⋅EDU, Free⋅FR( Proxad⋅NET )
Multikabel⋅NET( Ziggo⋅NL ), Linkpendium⋅COM( Panix⋅COM ), Xs4all⋅NL
Ediacara⋅ORG, Sdf-EU⋅ORG, Home⋅NL( Prolocation⋅NET )
With your "caret" ( text cursor ) within the BoLs you want to delete,
record this macro:
1. Hit Crl⋅F ( "Edit.Find", to bring up the find box ).
2. Search Up/Backwards for "^ ■$" ( RegEx ).
3. Search Down/Forwards for the same thing, "^ ■$".
4. Hit the close button (x), to close the find box.
5. Hit Crl⋅S ( "Edit.SelectToLastGoBack", to select the lines )
6. Hit Del ( to Delete the BoLs ).
7. Hit Down⋅Arrow+Home, so you're in the next block of lines.
Which becomes: ＜＜
Option Strict Off
Option Explicit Off
Public Module RecordingModule
DTE.Find.Backwards = True
DTE.Find.FindWhat = "^ ■$"
DTE.Find.Target = vsFindTarget.vsFindTargetCurrentDocument
DTE.Find.MatchCase = True
DTE.Find.MatchWholeWord = True
DTE.Find.MatchInHiddenText = False
DTE.Find.PatternSyntax = vsFindPatternSyntax.vsFindPatternSyntaxRegExpr
DTE.Find.Action = vsFindAction.vsFindActionFind
If (DTE.Find.Execute() = vsFindResult.vsFindResultNotFound) Then
Throw New System.Exception("vsFindResultNotFound")
DTE.Find.Backwards = False
If (DTE.Find.Execute() = vsFindResult.vsFindResultNotFound) Then
Throw New System.Exception("vsFindResultNotFound")
Now, you can Save/Rename/Move the macro,
so you can assign it to a Key⋅Hit and/or a Toolbar⋅Button,
Note: ＜＜ ^ ■$(^.*$)*^ ■$ ＞＞ doesn't work.
Small, fast, keypress macros are what I want. I don't need a full featured programming language.
Just one that plays keystrokes, can do a find and replace, cut and copy and paste.
While Sergey Vlasov's "Visual Commander" extension
doesn't record/playBack "Find" commands -- a HUGE omission --
it sounds promising.
Still, I see no reason to "upgrade" to a lesser product,
Visual Studio 2013.
Microsoft's biggest competitor is their prior work,
including the (displaced) programmers that wrote them.
Sergey Vlasov commented
The Visual Commander extension in the new version adds the ability to record and playback code editing commands and keystrokes in the Visual Studio 2010/2012/2013 text editor: