<?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>Detection logic for PowerShell installation</title><link>http://blogs.msdn.com/powershell/archive/2009/06/25/detection-logic-poweshell-installation.aspx</link><description>"How do we programmatically detect that PowerShell is installed ?" - This question has started coming up frequently as more folks (both internally and externally) have started to build applications with PowerShell support. As we approach Win7/W2K8-R2</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Detection logic for PoweShell installation</title><link>http://blogs.msdn.com/powershell/archive/2009/06/25/detection-logic-poweshell-installation.aspx#9803656</link><pubDate>Thu, 25 Jun 2009 17:30:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9803656</guid><dc:creator>Pter</dc:creator><description>&lt;p&gt;And what should we use to test it VBScript? LOLL&lt;/p&gt;</description></item><item><title>re: Detection logic for PoweShell installation</title><link>http://blogs.msdn.com/powershell/archive/2009/06/25/detection-logic-poweshell-installation.aspx#9804917</link><pubDate>Fri, 26 Jun 2009 10:28:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9804917</guid><dc:creator>Daniel</dc:creator><description>&lt;p&gt;Did you really spell PowerShell wrong in the article title!!&lt;/p&gt;</description></item><item><title>re: Detection logic for PowerShell installation</title><link>http://blogs.msdn.com/powershell/archive/2009/06/25/detection-logic-poweshell-installation.aspx#9805374</link><pubDate>Fri, 26 Jun 2009 15:46:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9805374</guid><dc:creator>PowerShellTeam</dc:creator><description>&lt;p&gt;@Daniel - thanks. &amp;nbsp;Fixed now.&lt;/p&gt;
&lt;p&gt;Enjoy!&lt;/p&gt;
&lt;p&gt;Jeffrey Snover [MSFT]&lt;/p&gt;
&lt;p&gt;Distinguished Engineer&lt;/p&gt;
&lt;p&gt;Visit the Windows PowerShell Team blog at: &amp;nbsp; &amp;nbsp;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/PowerShell"&gt;http://blogs.msdn.com/PowerShell&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Visit the Windows PowerShell ScriptCenter at: &amp;nbsp;&lt;a rel="nofollow" target="_new" href="http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx"&gt;http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Detection logic for PowerShell installation</title><link>http://blogs.msdn.com/powershell/archive/2009/06/25/detection-logic-poweshell-installation.aspx#9820130</link><pubDate>Mon, 06 Jul 2009 19:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9820130</guid><dc:creator>cz9qvh</dc:creator><description>&lt;p&gt;FYI, the ps installer won't set HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\PowerShell\1\Insall = 1... so if your app is 32 bit and running on 64 bit windows then this method won't work.&lt;/p&gt;</description></item><item><title>re: Detection logic for PowerShell installation</title><link>http://blogs.msdn.com/powershell/archive/2009/06/25/detection-logic-poweshell-installation.aspx#9905724</link><pubDate>Sat, 10 Oct 2009 10:34:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9905724</guid><dc:creator>Ken</dc:creator><description>&lt;p&gt;How do we detect PowerShell 2.0 (but not 1.0) in a manner that won't break when PowerShell 3.0 is released?&lt;/p&gt;</description></item></channel></rss>