-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not load type WebDriverWait #262
Comments
that class is no longer in WebDriver.Support |
Well, that would explain the issue. I have the feeling Seleno's been largely abandoned as a project? |
Let’s hope not |
@jimmymain I agree. I am trying to resolve, but the dependencies are all so out of date, it's hard to know where to begin :( |
I installed pre 5.2.1 and it works fine |
I wouldn’t say abandoned, but certainly all of the core maintainers have other focus areas and haven’t been investing time into it.
People still seem to be getting use out of it. If members of the community want to step up to inject some love we’d be happy to grant access to edit the repo.
… On 26 Oct 2017, at 9:49 pm, Sven Aelterman ***@***.***> wrote:
Well, that would explain the issue.
I have the feeling Seleno's been largely abandoned as a project?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@jimmymain I don't understand "pre 5.2.1"? Version 5.2.1 of what? |
So about two years later, and I've finally updated TestStack.Seleno. If anyone would like to try it out, it's here. I haven't update the .nuspec yet, and there are still some NuGet packages out of date. However, Seleno now works with the latest Selenium (3.141). @robdmoore I will submit a PR, but be aware it's a huge changeset. |
@robdmoore Update: PR submitted: #267 |
When using Selenium 3.5.2 or higher, I get this exception:
Could not load type 'OpenQA.Selenium.Support.UI.WebDriverWait' from assembly 'WebDriver.Support, Version=3.6.0.0, Culture=neutral, PublicKeyToken=null'
Based on the stacktrace, the exception is triggered by ElementFinder.cs line 24.
I can't find anything in the Selenium release notes that would indicate a potential cause.
The text was updated successfully, but these errors were encountered: