Thank you for the reply.
When using VS with a .NET framework project if we install the package WITHOUT the version flag, it works. We've noticed that the -beta.2 version does not indicate "prerelease" if that matters.
This is a constant issue when we update Selenium.
When we don't use ProGet it works so that's what lead us to believe it was a ProGet related issue.
Works from the web UI without issue.
We tested installing the package in a .NET Core console app and a .NET Framework console app
(core being PackageReference style and Framework being packages.config style) and found that
the Core project installed just fine, but the Framework project was only able to install the
package if we omit the -Version argument using the Package Manager Console in VS.
I ran the below in the package manager window of both.
install-package Selenium.WebDriver.ChromeDriver -Version 103.0.5060.5300 -Source https://(redacted)/nuget/approved-nuget/v3/index.json
Test console app 1 - .Net Core 3.1 LTS
Test console app 2 - .Net Framework 4.7.2
dward_2542's message should have been
nuget install Selenium.WebDriver.ChromeDriver -Version 103.0.5060.5300 -Source https://--redacted--/nuget/approved-nuget/v3/index.json
Package 'Selenium.WebDriver.ChromeDriver 103.0.5060.5300' is not found in the following primary source(s): --redacted--/nuget/approved-nuget/v3/index.json'. Please verify all your online package sources are available (OR) package id, version are specified correctly.
He asked me to update this thread.