Huddled Masses - Latest Comments in Window GUI Automation from PowerShell

Re: Window GUI Automation from PowerShell

Jaykul — Sat, 11 Oct 2008 21:49:10 -0000

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...

Re: Window GUI Automation from PowerShell

seaJhawk — Sat, 11 Oct 2008 19:40:02 -0000

Hi Jaykul,
My app that I'm trying to automate pops up a modal dialog when I click a key. However, I can't find any way to select that modal dialog - should this be possible?

Thanks,
seaJhawk

Re: Window GUI Automation from PowerShell

Jaykul — Thu, 18 Sep 2008 08:28:04 -0000

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

Re: Window GUI Automation from PowerShell

rama — Thu, 18 Sep 2008 07:05:00 -0000

hi,

If I do Add-module I am getting this error.

F:\windowautomation>
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 <<<< .\WindowAutomation

Re: Window GUI Automation from PowerShell

rama — Thu, 18 Sep 2008 07:00:44 -0000

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

Re: Window GUI Automation from PowerShell

Jaykul — Wed, 17 Sep 2008 23:26:32 -0000

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.

Re: Window GUI Automation from PowerShell

rama — Wed, 17 Sep 2008 01:36:58 -0000

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

Re: Window GUI Automation from PowerShell

Jaykul — Wed, 21 May 2008 13:30:12 -0000

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 | ? {$_.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:


$np = Select-Window notepad
Send-Keys $np "what?"
Select-Window notepad | Send-Keys "%{f4}n"

Re: Window GUI Automation from PowerShell

Evan — Mon, 19 May 2008 10:42:23 -0000

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 | 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

Re: Window GUI Automation from PowerShell

George Davis — Tue, 01 Apr 2008 10:15:02 -0000

Thanks for writing this, Joel! I've used it to automate the installation of our product on my development laptop, which I have to do very frequently. I've had a batch file for a year that would un-install the product but didn't want to load our QA app just to automate the install. Now I've done it with your DLL and PowerShell in a very lightweight fashion! I wrote a PowerShell script to read an "instruction" file that looks like:

RUN,c:\temp\setup.exe
SLEEP,15
WINDOW,msiexec
KEYS,{ENTER}
SLEEP,2
KEYS,{UP}
KEYS,{ENTER}
SLEEP,2
KEYS,{ENTER}
SLEEP,2
KEYS,{ENTER}
SLEEP,2
KEYS,{ENTER}
SLEEP,2
KEYS,{TAB}
KEYS,{TAB}
KEYS,{TAB}
KEYS,mySqlPassword
KEYS,{TAB}
KEYS,{END}
KEYS,\SQL2005
KEYS,{ENTER}
SLEEP,2
KEYS,{ENTER}
SLEEP,2
KEYS,{ENTER}
SLEEP,2
KEYS,{ENTER}
SLEEP,2
KEYS,{ENTER}
SLEEP,2
KEYS,{ENTER}
SLEEP,2
WAITFORBUTTON,&Finish,10,{ENTER}

The WINDOW instruction is only specified at the beginning of the file so that when the script reads the KEYS command, it knows which window to which to send the keystrokes. On most of the screens, I just hit enter but you can probably see one where I enter a SQL password.

My script reads each line and executes the appropriate command using your DLL. I still have the RUN one to complete but everything else works. The WAITFORBUTTON instruction will cause my script to look for the Finish button and it not found, keep checking every 10 seconds and when found, hit Enter.

Again, when I get the RUN instruction implemented, I'll send you the PS1 file and a sample instruction file. My network admin guy drooled a lot when he saw what I had done and wants to automate all the boring installs/upgrades he has to do all the time.

Many thanks again!
George