Open Ketenks opened 4 years ago
Confirmed, I am not sure how powershell module dlls are really suppose to work, but this is what I get
Get-Command -Module WASP
CommandType Name Version Source
----------- ---- ------- ------
Cmdlet Select-Window 2.0.0.0 WASP
Cmdlet Send-Keys 2.0.0.0 WASP
Cmdlet Send-Mouse 2.0.0.0 WASP
Cmdlet Set-Focus 2.0.0.0 WASP
Cmdlet Set-Text 2.0.0.0 WASP
Oh I see, the "release" from github is an older version than is available on the gallery. If I install via
Install-Module -Name WASP
then it installed version 2.5.00, with many more commands.
Although I still can not find actual documentation anywhere, it definitely does not correspond to this repository's readme.
So confusing! I downloaded the code, opened sln in VS and built the WindowsAutomation project (not WASP) and the DLL it generated is the one that matches the instructions. I had an old script using WASP I needed to make work again and had to do this. No idea what the other version that's in the gallery is, it's really different.
I followed the instructions to install WASP into my Program Files\WindowsPowershell\Modules directory.
I unblocked the WASP.dll file that was in the Builds\Release directory but was put into the WASP directory.
I imported the module successfully and tried to Get-WindowPosition and it said that this command was not recognized.
I see the commands which are missing in the WindowsAutomation directory but this directory is not included in the WASP directory that is imported into the Powershell modules.
I do not know how to fit those in to make them work. But I think the directions need to specify exactly how to do a complete installation of this snapin.