or Create a profile
08 Nov, 2019 02:27 PM
We are using Selenium and Chromedriver for unit testing and locally have the latest Chrome installed, currently 78, but the appveyor build images only support up to 77. I am trying to find a way to have the Selenium.WebDriver.ChromeDriver nuget package downgraded before the build process so that we don't have to worry about the package versions locally.
Microsoft has the Update-Package powershell cmdlet but its only available from the nuget console. Is there a way to run nuget console commands in the build process? Or another way to accomplish what I am trying to do? Preferably without doing like a manual string replace on the packages.config and .csproj.
on 08 Nov, 2019 10:18 PM
Sure, you can use nuget command line client which is pre-installed on build VMs. Also, you can upgrade Chrome to the latest version with Chocolatey: choco install googlechrome.
choco install googlechrome
Btw, we've just deployed updated build VM images with the latest Chrome 78 installed.
on 12 Nov, 2019 02:33 PM
Where can those commands be run from? The "before build script" as Cmd or?
on 12 Nov, 2019 07:22 PM
Yep...and as I previously noted we've updated build images with the latest Chrome.
Formatting help /
(switch to plain text)
(switch to Markdown)
You can attach files up to 10MB
If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.
A conversation has been started with the AppVeyor staff to resolve this discussion.
This discussion is private.
Only you and AppVeyor support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
You can use Command ⌘ instead of Control ^ on Mac
Powered by Tender™.