Open
Description
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.
- Publish Exes.zip to GitHub.com/Microsoft/WinAppDriver along with MSI
- 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.