Re: Why is webdriver.dll for C# not updated?

[Jim Evans]

Well, for one thing, the 3.141 of the .NET bindings was released in October of 2018, not August. For another, it likely wouldn’t change anything. The problem with your StaleElementException is most likely a problem in the *driver* not the bindings. Finally, all effort on the .NET bindings since that last public release has been on the 4.0 alpha releases.

On Monday, May 11, 2020 at 4:53:10 AM UTC-4, Michael Baas wrote:

According to the downloads-page, the Java-Driver is @ version 3.141.59 (Nov 2018), while C# is still @ 3.141.0 (Aug 2018). 

I have a case of an unjustified stale-element-exception, and this answer on stackoverflow suggests that the error had been fixed with 3.141.59 - so I wonder why the C#-Driver was not rebuild for such a long time?

[Michael Baas]

Well, for one thing, the 3.141 of the .NET bindings was released in October of 2018, not August.

Ok. I was just quoting from the downloads-page:

 

For another, it likely wouldn’t change anything. The problem with your StaleElementException is most likely a problem in the *driver* not the bindings.

The quoted answer on stackoverflow seemed to suggest using 3.141.159, but reading it again, I may have misunderstood. Can reproduce with gecko- and chromedriver, though. 

  

Finally, all effort on the .NET bindings since that last public release has been on the 4.0 alpha releases.

I'm looking at 4 as well - but that causes different problems (which I'm trying to dig into atm).

 

On Monday, May 11, 2020 at 4:53:10 AM UTC-4, Michael Baas wrote:

According to the downloads-page, the Java-Driver is @ version 3.141.59 (Nov 2018), while C# is still @ 3.141.0 (Aug 2018). 

I have a case of an unjustified stale-element-exception, and this answer on stackoverflow suggests that the error had been fixed with 3.141.59 - so I wonder why the C#-Driver was not rebuild for such a long time?

[Joe Ward]

I don't understand what you're saying. The screenshot you posted says 3.14.0 on August 02 2018. 

3.14.0 != 3.1410, which was indeed in October if you cross-reference with this https://www.nuget.org/packages/Selenium.WebDriver/3.141.0.

Generally the problem you are having is indeed more to do with the driver than the bindings so I would suggest you may have misread.. I'd certainly trust Jim on the matter either way... any chance you can show us the code you are using so we can assess?

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/78996973-a7a1-465e-b78f-c3320be4c33a%40googlegroups.com.

[Michael Baas]

Ok, used the wrong version number. I was referring to 3.14.0 (Aug 2, 2018). The downloads-page also says "Nuget latest release is 3.14.0. Released on 2018-08-02" - but the page it links to shows version 3.141.0 - that confused me a bit, I think.

But I'm glad to report that the problem I saw (MoveTo not moving to the right element) was because MoveTo did not get the right argument. There is a problem with the assignment of that argument - but that problem may well be on my end.. I guess we can close this case then ;)

Thanks

Michael

To unsubscribe from this group and stop receiving emails from it, send an email to seleniu...@googlegroups.com.