<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Window GUI Automation from PowerShell</title>
	<atom:link href="http://huddledmasses.org/window-gui-automation-from-powershell/feed/" rel="self" type="application/rss+xml" />
	<link>http://huddledmasses.org/window-gui-automation-from-powershell/</link>
	<description>You can do more than breathe for free...</description>
	<pubDate>Fri, 21 Nov 2008 03:28:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jaykul</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-205493</link>
		<dc:creator>Jaykul</dc:creator>
		<pubDate>Wed, 15 Oct 2008 13:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-205493</guid>
		<description>Yes it should!  At the very least you should be able to select it as the "active" window</description>
		<content:encoded><![CDATA[<p>Yes it should!  At the very least you should be able to select it as the &#8220;active&#8221; window</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaykul</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-205492</link>
		<dc:creator>Jaykul</dc:creator>
		<pubDate>Sun, 12 Oct 2008 00:49:10 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-205492</guid>
		<description>Yeah, that should be possible. If it's modal, it should be the "active" window anyway, so you should be able to get it that way, or just send-keys and have them go to it by default...</description>
		<content:encoded><![CDATA[<p>Yeah, that should be possible. If it&#8217;s modal, it should be the &#8220;active&#8221; window anyway, so you should be able to get it that way, or just send-keys and have them go to it by default&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: seaJhawk</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-204550</link>
		<dc:creator>seaJhawk</dc:creator>
		<pubDate>Sat, 11 Oct 2008 23:40:02 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-204550</guid>
		<description>Hi Jaykul,&lt;br&gt;My app that I&#39;m trying to automate pops up a modal dialog when I click a key. However, I can&#39;t find any way to select that modal dialog - should this be possible?&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;seaJhawk</description>
		<content:encoded><![CDATA[<p>Hi Jaykul,<br />
My app that I&#39;m trying to automate pops up a modal dialog when I click a key. However, I can&#39;t find any way to select that modal dialog &#8211; should this be possible?</p>
<p>Thanks,<br />
seaJhawk</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel 'Jaykul' Bennett</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-195758</link>
		<dc:creator>Joel 'Jaykul' Bennett</dc:creator>
		<pubDate>Thu, 18 Sep 2008 12:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-195758</guid>
		<description>For CTP2, you need to *either* put the dll into a specific folder ... @Documents\WindowsPowerShell\Packages\WindowsAutomation\WindowsAutomation.dll@ in which case you'll be able to call just:

Add-Module WindowsAutomation

Otherwise, you can load it by specifying the path to the actual .dll:

Add-Module .\WindowsAutomation.dll</description>
		<content:encoded><![CDATA[<p>For CTP2, you need to <strong>either</strong> put the dll into a specific folder &#8230; <code>Documents\WindowsPowerShell\Packages\WindowsAutomation\WindowsAutomation.dll</code> in which case you&#8217;ll be able to call just:</p>
<p>Add-Module WindowsAutomation</p>
<p>Otherwise, you can load it by specifying the path to the actual .dll:</p>
<p>Add-Module .\WindowsAutomation.dll</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rama</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-195733</link>
		<dc:creator>rama</dc:creator>
		<pubDate>Thu, 18 Sep 2008 11:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-195733</guid>
		<description>hi,

 If I do Add-module I am getting this error.

 F:\windowautomation&#62; 
Add-Module .\WindowAutomation
Add-Module : The specified module '.\WindowAutomation' was not loaded because the module source file was not found in any package 
directory, 
At line:1 char:11
+ Add-Module &#60;&#60;&#60;&#60;  .\WindowAutomation</description>
		<content:encoded><![CDATA[<p>hi,</p>
<p> If I do Add-module I am getting this error.</p>
<p> F:\windowautomation&gt;<br />
Add-Module .\WindowAutomation<br />
Add-Module : The specified module &#8216;.\WindowAutomation&#8217; was not loaded because the module source file was not found in any package<br />
directory,<br />
At line:1 char:11<br />
+ Add-Module &lt;&lt;&lt;&lt;  .\WindowAutomation</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rama</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-195730</link>
		<dc:creator>rama</dc:creator>
		<pubDate>Thu, 18 Sep 2008 11:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-195730</guid>
		<description>Hi, 
 
 I am using CTP2 only can you please guide me how can I install 

bacaz Installutil is  not recognised  as a cmdlet. It will be helpful for me  how to  install the  GUI Automation Snapin from the scrach.

Do I need any other .exe  to proceed the installation. The snapin which is not working out for me.

thanks in advance</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p> I am using CTP2 only can you please guide me how can I install </p>
<p>bacaz Installutil is  not recognised  as a cmdlet. It will be helpful for me  how to  install the  <span class="caps">GUI</span> Automation Snapin from the scrach.</p>
<p>Do I need any other .exe  to proceed the installation. The snapin which is not working out for me.</p>
<p>thanks in advance</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel 'Jaykul' Bennett</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-195640</link>
		<dc:creator>Joel 'Jaykul' Bennett</dc:creator>
		<pubDate>Thu, 18 Sep 2008 03:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-195640</guid>
		<description>You need to run "Get-Help about_signing" as it suggests.  By default PowerShell requires everything to be cryptographically signed.  My stuff isn't, so you have to use the "Set-ExecutionPolicy" cmdlet to set your policy to "RemoteSigned"... and you might have to "unblock" the script (this is all described in the "Get-Help about_signing" document.

If you're using CTP2, you can use Add-Module instead of using the installer.

Also, you should use the version on "CodePlex":http://CodePlex.com/WASP because it's been updated from the one I posted. I've changed that in the article.</description>
		<content:encoded><![CDATA[<p>You need to run &#8220;Get-Help about_signing&#8221; as it suggests.  By default PowerShell requires everything to be cryptographically signed.  My stuff isn&#8217;t, so you have to use the &#8220;Set-ExecutionPolicy&#8221; cmdlet to set your policy to &#8220;RemoteSigned&#8221;... and you might have to &#8220;unblock&#8221; the script (this is all described in the &#8220;Get-Help about_signing&#8221; document.</p>
<p>If you&#8217;re using CTP2, you can use Add-Module instead of using the installer.</p>
<p>Also, you should use the version on <a href="http://CodePlex.com/WASP">CodePlex</a> because it&#8217;s been updated from the one I posted. I&#8217;ve changed that in the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rama</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-195428</link>
		<dc:creator>rama</dc:creator>
		<pubDate>Wed, 17 Sep 2008 05:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-195428</guid>
		<description>Hi,

   How can I install the windows automation snapin in my power shell environment. I am getting an error like 

File C:\Documents and settings\test\Desktop\windowautomation\WindowAutomation\Install.ps1 cannot be loaded. The file C:\Documents and Settings\test\Desktop\windowautomation\WindowAutomation\Install.ps1 is not digitally signed. The script will not execute on the system. Please see "get-help about_signing" for more details..
At line:0 char:0</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>   How can I install the windows automation snapin in my power shell environment. I am getting an error like </p>
<p>File C:\Documents and settings\test\Desktop\windowautomation\WindowAutomation\Install.ps1 cannot be loaded. The file C:\Documents and Settings\test\Desktop\windowautomation\WindowAutomation\Install.ps1 is not digitally signed. The script will not execute on the system. Please see &#8220;get-help about_signing&#8221; for more details..<br />
At line:0 char:0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel 'Jaykul' Bennett</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-158252</link>
		<dc:creator>Joel 'Jaykul' Bennett</dc:creator>
		<pubDate>Wed, 21 May 2008 17:30:12 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-158252</guid>
		<description>Hm, looks like I messed up the parameter sets somehow. I'll have to push out a new release on CodePlex.

Select-Window doesn't seem to like selecting the console windows ... and I don't know why (that is to say, I'll have to crack the code open, so gimme a few days). They show up if you do @Select-Window &#124; ? {$_.ProcessName -eq "powershell"}@ ...

Get-WindowPosition and Remove-Window are broken because I messed up their parameter sets -- they can't resolve which parameter set to use, because they have two sets which are basically identical. That was a typo on my part.  Luckily, you can use the @Position@ attribute on the Window objects, and the CloseMainWindow() and CloseProcess() methods...

Send-Keys seems to work fine here ... either via the pipeline or as an argument:

&lt;code lang="posh"&gt;
$np = Select-Window notepad
Send-Keys $np "what?"
Select-Window notepad &#124; Send-Keys "%{f4}n"&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Hm, looks like I messed up the parameter sets somehow. I&#8217;ll have to push out a new release on CodePlex.</p>
<p>Select-Window doesn&#8217;t seem to like selecting the console windows &#8230; and I don&#8217;t know why (that is to say, I&#8217;ll have to crack the code open, so gimme a few days). They show up if you do <code>Select-Window | ? {$_.ProcessName -eq &#34;powershell&#34;}</code> &#8230;</p>
<p>Get-WindowPosition and Remove-Window are broken because I messed up their parameter sets &#8212; they can&#8217;t resolve which parameter set to use, because they have two sets which are basically identical. That was a typo on my part.  Luckily, you can use the <code>Position</code> attribute on the Window objects, and the CloseMainWindow() and CloseProcess() methods&#8230;</p>
<p>Send-Keys seems to work fine here &#8230; either via the pipeline or as an argument:</p>
<div class="code posh" style="font-family: monospace;">
<span style="color: #660033; font-weight: bold;">$np</span> = <span style="color: #0066cc; font-style: italic;">Select-<span style="font-style: normal;">Window</span></span> notepad<br />
<span style="color: #0066cc; font-style: italic;">Send-<span style="font-style: normal;">Keys</span></span> <span style="color: #660033; font-weight: bold;">$np</span> <span style="color: #009900;">&quot;what?&quot;</span><br />
<span style="color: #0066cc; font-style: italic;">Select-<span style="font-style: normal;">Window</span></span> notepad | <span style="color: #0066cc; font-style: italic;">Send-<span style="font-style: normal;">Keys</span></span> <span style="color: #009900;">&quot;%{f4}n&quot;</span><br />
&nbsp;</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan</title>
		<link>http://huddledmasses.org/window-gui-automation-from-powershell/comment-page-1/#comment-157735</link>
		<dc:creator>Evan</dc:creator>
		<pubDate>Mon, 19 May 2008 14:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://HuddledMasses.org/window-gui-automation-from-powershell/#comment-157735</guid>
		<description>I am having some problems running this code.  Here are some of them I've run across so far:

1)for some strange reason "select-window *powershell*" doesn't return anything even though "select-window *notepad*"  does

for the following problems, "$window = select-window *notepad*"

2)Both "get-windowposition $window" and "$window &#124; get-windowposition" will not recognize $window as a parameter

This happens with remove-window, and send-keys

3) "set-windowposition -width 2" does nothing and "set-windowposition $window -maximize " gives and error


I can send the code I am trying with the errors if necessary</description>
		<content:encoded><![CDATA[<p>I am having some problems running this code.  Here are some of them I&#8217;ve run across so far:</p>
<p>1)for some strange reason &#8220;select-window <strong>powershell</strong>&#8220; doesn&#8217;t return anything even though &#8220;select-window <strong>notepad</strong>&#8220;  does</p>
<p>for the following problems, &#8220;$window = select-window <strong>notepad</strong>&#8220;</p>
<p>2)Both &#8220;get-windowposition $window&#8221; and &#8220;$window | get-windowposition&#8221; will not recognize $window as a parameter</p>
<p>This happens with remove-window, and send-keys</p>
<p>3) &#8220;set-windowposition -width 2&#8221; does nothing and &#8220;set-windowposition $window -maximize &#8220; gives and error</p>
<p>I can send the code I am trying with the errors if necessary</p>
]]></content:encoded>
	</item>
</channel>
</rss>
