-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commands Not Existing #4
Comments
Confirmed, I am not sure how powershell module dlls are really suppose to work, but this is what I get
Oh I see, the "release" from github is an older version than is available on the gallery.
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.
The text was updated successfully, but these errors were encountered: