lyon-smith.org

I don't write many Outlook macros primarily because I don't have time to learn the CDO document model.  But once upon a time I wrote a couple of macros that have become invaluable to me ever since.  Some background.  I process my e-mail roughly like this: I use Outlook rules to filter out e-mail that is sent to most of ...

Don't ask why, but I needed to list all the properties of all the projects in a solution.  Here's the macro that did it for me: Sub ListProjectProperties() Dim pane As EnvDTE.OutputWindowPane pane = Utilities.GetOutputWindowPane(''Output'') Dim projects As EnvDTE.Projects projects = ...

Here's another useful VS macro.  When I write code there are always weird edge cases that I think of while so I like to liberally sprinkle // TODO: comments around.  When you do this though you should always put in your alias and the date.  That way someone who comes across your comment knows who to ask for further details, or ...

Some things that should be easy are still much harder than they should be.  One of those things is writing macros and add-ins for Visual Studio. The object hierachy is (a) obfuscated by a COM/managed interop mess (b) not logically or consistently laid out (c) hard to debug, (d) full of subtle bugs and weird behaviors. Today I ...

One of the most useful macros I ever wrote in VS was but a single line.  All it does is insert a GUID at the current selection point.  It was so useful I wrote it twice; once to insert lowercase and once to insert uppercase GUIDs.  Here it is:Imports System Imports EnvDTE Imports EnvDTE80 Imports System.Diagnostics Public ...

I've always loved editors with built in macro languages. Once you have macro control of every facet of the editor you can pull off some really cool and time saving tricks. I gave up macros back in the early 90's for the graphical environment of Microsoft Quick C, Developer Studio and now Visual Studio. So I was overjoyed to see macros make a real ...