Skip to content

Ship WinAppDriver binaries as zip package together with MSI files and allow WinAppDriver to be run in any folder #913

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

Open
licanhua opened this issue Oct 14, 2019 · 0 comments

Comments

@licanhua
Copy link
Contributor

MSI requires admin permission to install it, and it's a problem in Azure pipeline

Actually the binary of WinAppDriver can be run without admin permission, and here is the proposal to workaround the privilege problem.

  1. Publish Exes.zip to GitHub.com/Microsoft/WinAppDriver along with MSI
  2. Update Appium-windows-driver to use Exec.zip install of MSI.

Allow customer to add full path to WinAppDriver.exe in WinAppDriver Pipelines Task which Hassan maintained.

This is what chromedriver did. Instead of packaging binary in npm, it downloads ChromeDriver from http://chromedriver.storage.googleapis.com when install the package.

In appium-windows-driver, we download and install WinAppDriver MSI too.
but Appium-windows-driver needs customer to run as admin to install MSI, actually we should not recommend customer to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants