Trying to have the latest version of ChromeDriver without having to always update the Nuget: Selenium.WebDriver.ChromeDriver in drop folder.
For this we used the floating variable: "*" for version as below in my project .csproj file:
<PackageReference Include="Selenium.WebDriver.ChromeDriver" Version="*"/>
or
<PackageReference Include="Selenium.WebDriver.ChromeDriver"><Version>*</Version></PackageReference>
This works in local wherein on build, the latest version of available chromedriver ( currently: 99.0.4844.5100 ) is installed into local machine in bin/debug (or whichever)
but using a floating variable doesn't copy the latest ChromeDriver.exe (or any version of ChromeDriver.exe) into the build drop.
Any other way of using floating variable works: For example:
- using 99* works (but this will always fix it to any version starting with 99, and will not get the next highest version when the next version 100 will release
- using []/(]/()/[) works but again will not get the highest acceptable stable version
- hardcoding the version like 99.0.4844.5100 works
Note: My goal is to
- Not manually keep updating Selenium.WebDriver.ChromeDriver in my projects
- Have latest publish to build drop folder upon checkin
- Copy build files to a remote VM X
- Use the latest ChromeDriver.exe copied onto the machine X to run Selenium Test Cases using latest Nuget without manually and continuously checking and updating Nuget SeleniumWebDriver.ChromeDriver for a new version.
How can we move latest highest version of chromedriver.exe to build drop upon check-in without having to manually regularly updating the Nuget package: Selenium.WebDriver.ChromeDriver ? (preferebly by using * in version of csproj) ?