<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Aaron Marten : Automation</title><link>http://blogs.msdn.com/aaronmar/archive/tags/Automation/default.aspx</link><description>Tags: Automation</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Extension Manager</title><link>http://blogs.msdn.com/aaronmar/archive/2008/11/04/extension-manager.aspx</link><pubDate>Tue, 04 Nov 2008 16:40:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9039361</guid><dc:creator>aaronmar</dc:creator><slash:comments>6</slash:comments><comments>http://blogs.msdn.com/aaronmar/comments/9039361.aspx</comments><wfw:commentRss>http://blogs.msdn.com/aaronmar/commentrss.aspx?PostID=9039361</wfw:commentRss><wfw:comment>http://blogs.msdn.com/aaronmar/rsscomments.aspx?PostID=9039361</wfw:comment><description>&lt;p&gt;One of the new features we plan on shipping for VS 2010 that I've been heads down on for the past few months is the &amp;quot;Extension Manager&amp;quot;. I'll be posting more details about it here over the next several months.&lt;/p&gt;  &lt;p&gt;For the meantime, you can hear more about it (and see some very early mockups) in &lt;a href="http://channel9.msdn.com/pdc2008/TL32/"&gt;Dr. Tim Wagner's PDC talk&lt;/a&gt;. The part about the Extension Manager starts around 50:20. The earlier parts of the talk discuss some of the other new features that we're working on, including the new MEF-based editor extensibility model, &lt;a href="http://www.visualstudiogallery.com/"&gt;the VS Gallery&lt;/a&gt;, and a general introduction to VS extensibility.&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9039361" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Visual+Studio+SDK/default.aspx">Visual Studio SDK</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Automation/default.aspx">Automation</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/VSX/default.aspx">VSX</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Visual+Studio+Shell/default.aspx">Visual Studio Shell</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Extension+Manager/default.aspx">Extension Manager</category></item><item><title>Match Options Command Addin</title><link>http://blogs.msdn.com/aaronmar/archive/2008/03/21/match-options-command-addin.aspx</link><pubDate>Fri, 21 Mar 2008 20:56:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8329658</guid><dc:creator>aaronmar</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/aaronmar/comments/8329658.aspx</comments><wfw:commentRss>http://blogs.msdn.com/aaronmar/commentrss.aspx?PostID=8329658</wfw:commentRss><wfw:comment>http://blogs.msdn.com/aaronmar/rsscomments.aspx?PostID=8329658</wfw:comment><description>&lt;p&gt;A while back, there was some &lt;a href="http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=979409&amp;amp;SiteID=1&amp;amp;mode=1"&gt;interest on the VSX forum&lt;/a&gt; around adding back functionality to have "Match Case" and "Match Whole Word" buttons on the toolbar in Visual Studio 2005. At the time, I created a little addin to do this and just posted it to a website I had access to.&lt;/p&gt; &lt;p&gt;In the meantime, I accidentally deleted the files from the web server (oops). Also, some folks have been asking if there was a version that works with Visual Studio 2008.&lt;/p&gt; &lt;p&gt;&lt;a href="http://blogs.msdn.com/blogfiles/aaronmar/WindowsLiveWriter/MatchOptionsCommandAddin_9872/screenshot_2.png"&gt;&lt;img style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px" height="223" alt="screenshot" src="http://blogs.msdn.com/blogfiles/aaronmar/WindowsLiveWriter/MatchOptionsCommandAddin_9872/screenshot_thumb.png" width="644" border="0"&gt;&lt;/a&gt; &lt;/p&gt; &lt;p&gt;I've set up a &lt;a href="http://code.msdn.microsoft.com/vsmatchoptions"&gt;page on the MSDN Code Gallery&lt;/a&gt; to be a permanent home for this addin. I've released files that will allow you to install the addin for both Visual Studio 2005 &amp;amp; 2008. You can also download the sources if you're interested. Please open any bugs you find on the Issue Tracker page. Enjoy!&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8329658" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Powertoys/default.aspx">Powertoys</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Automation/default.aspx">Automation</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/VSX/default.aspx">VSX</category></item><item><title>VSX Videos on Channel 9</title><link>http://blogs.msdn.com/aaronmar/archive/2008/02/27/vsx-videos-on-channel-9.aspx</link><pubDate>Wed, 27 Feb 2008 20:08:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7920133</guid><dc:creator>aaronmar</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/aaronmar/comments/7920133.aspx</comments><wfw:commentRss>http://blogs.msdn.com/aaronmar/commentrss.aspx?PostID=7920133</wfw:commentRss><wfw:comment>http://blogs.msdn.com/aaronmar/rsscomments.aspx?PostID=7920133</wfw:comment><description>&lt;p&gt;Yesterday, Ken Levy and I sat down with Dan from &lt;a href="http://channel9.msdn.com"&gt;Channel 9&lt;/a&gt; to have an unscripted discussion about Visual Studio Extensibility (VSX) (including finding a bug live during an untested, on-the-fly demo!). We also discussed creating your own Visual Studio Shell and show off how to add a new package to a VS Shell application, among other things. Check it out:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://channel9.msdn.com/Showpost.aspx?postid=386366"&gt;Ken and Aaron discuss VSX&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;In another video, Anthony and Ken also show off the Visual Studio Gallery that was announced this morning:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://channel9.msdn.com/Showpost.aspx?postid=386361"&gt;Anthony and Ken discuss the Visual Studio Gallery&lt;/a&gt;&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7920133" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Visual+Studio+SDK/default.aspx">Visual Studio SDK</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Managed+Language+Tools/default.aspx">Managed Language Tools</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Automation/default.aspx">Automation</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/VSX/default.aspx">VSX</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Visual+Studio+Shell/default.aspx">Visual Studio Shell</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/DSL+Tools/default.aspx">DSL Tools</category></item><item><title>Scripting Visual Studio with Windows PowerShell</title><link>http://blogs.msdn.com/aaronmar/archive/2007/02/06/scripting-visual-studio-with-windows-powershell.aspx</link><pubDate>Tue, 06 Feb 2007 19:34:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1612663</guid><dc:creator>aaronmar</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/aaronmar/comments/1612663.aspx</comments><wfw:commentRss>http://blogs.msdn.com/aaronmar/commentrss.aspx?PostID=1612663</wfw:commentRss><wfw:comment>http://blogs.msdn.com/aaronmar/rsscomments.aspx?PostID=1612663</wfw:comment><description>&lt;p&gt;One of the really cool new things that shipped recently that I've been trying to learn more about is &lt;a href="http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx"&gt;Windows Powershell&lt;/a&gt;. What's really great about it is that if your object supports COM or .NET, you can automate it just by firing up the command line.&lt;/p&gt; &lt;p&gt;To get an instance of Visual Studio running, I can do the following :&lt;/p&gt; &lt;p&gt;$dte = New-Object -comobject "VisualStudio.DTE"&lt;/p&gt; &lt;p&gt;(Note that if you have multiple versions installed you can specify VisualStudio.DTE&lt;strong&gt;.7.0 &lt;/strong&gt;for VS 2002, VisualStudio.DTE&lt;strong&gt;.7.1 &lt;/strong&gt;for VS 2003 or VisualStudio.DTE&lt;strong&gt;.8.0 &lt;/strong&gt;for VS 2005.)&lt;/p&gt; &lt;p&gt;Since the DTE object was created via code and not by a user action, VS runs in silent mode (no user interface shown). I can show the main form with:&lt;/p&gt; &lt;p&gt;$dte.MainWindow.Visible = $true&lt;/p&gt; &lt;p&gt;For a useless example, if I want to close all the windows in the shell, I can do the following:&lt;/p&gt; &lt;p&gt;foreach ($w in $dte.Windows) { $w.Close() }&lt;/p&gt; &lt;p&gt;The cool thing about this really isn't that I can script Visual Studio (I could already do that from IronPython, VBScript or any other environment that can talk to COM objects), but that I can do it from the same command line that I use for other tasks in Windows.&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1612663" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/aaronmar/archive/tags/PowerShell/default.aspx">PowerShell</category><category domain="http://blogs.msdn.com/aaronmar/archive/tags/Automation/default.aspx">Automation</category></item></channel></rss>