Can't automatically build packages

[leandrodotec]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Get one day where LATEST_STABLE does not contain win32, win64, linux and mac
2. Run build action

Expected behavior It should build a package with whatever is available.

Screenshots

Additional context Add any other context about the problem here.

[leandrodotec]

If anyone has an idea, please type it in here :-)

[leandrodotec]

Created PR to try to fix these: #49

[leandrodotec]

Now the trick here is that we might need to run this daily or once every 2 days. But we will never know if the latest release has all files, or just windows, or just linux.

[icnocop]

This is interesting.

This issue is causing build issues for me.

For example, given the following in my .csproj: <PackageReference Include="Selenium.WebDriver.MSEdgeDriver" Version="*" />

I get the following error:

C:\Users\UserName\.nuget\packages\selenium.webdriver.msedgedriver\127.0.2651.107\build\Selenium.WebDriver.MSEdgeDriver.targets(88,5): error MSB3030: Could not copy the file "C:\Users\UserName\.nuget\packages\selenium.webdriver.msedgedriver\127.0.2651.107\build\..\driver\win32\msedgedriver.exe" because it was not found. [c:\agent\_work\1\s\MySolution\MyProject\MyProject.csproj::TargetFramework=net472]

[icnocop]

I'm wondering if we should split the NuGet packages?

For example: Selenium.WebDriver.MSEdgeDriver.x86 Selenium.WebDriver.MSEdgeDriver.x64 Selenium.WebDriver.MSEdgeDriver.ARM64 Selenium.WebDriver.MSEdgeDriver.MacM1 Selenium.WebDriver.MSEdgeDriver.Mac Selenium.WebDriver.MSEdgeDriver.Linux

In this way, each package can have it's own version.

[icnocop]

There are URLS which we can use to determine the latest version for each operating system specific version. For example:

https://msedgedriver.azureedge.net/LATEST_RELEASE_128_WINDOWS https://msedgedriver.azureedge.net/LATEST_RELEASE_128_MACOS https://msedgedriver.azureedge.net/LATEST_RELEASE_128_LINUX