Skip to content
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

[dotnet] Be more friendly for single file publishing and native compilation #12045

Merged
merged 7 commits into from
May 16, 2023
Merged

[dotnet] Be more friendly for single file publishing and native compilation #12045

merged 7 commits into from
May 16, 2023

Conversation

nvborisenko
Copy link
Member

Description

No major changes, just use APIs which are supported in native compilation.

Motivation and Context

Selenium is a library, and I don't see reasons why this library cannot be friendly for native compilation.

Addresses:

Area to be improved

"selenium-manager.exe" is packed in nuget package. When user consumes nuget package, then binaries (for all platforms) are copied to user's output. In case of single file publishing the situation is resolved in this PR - binaries are copied to output as they are expected to be there.

In case of native compilation (PublishAOT build property we need to be smarter:

  • Include selenium-manager as embedded resource into user's assembly
  • Try to look up selenium-manager from embedded resources if there are no binaries on the disk

Copy link
Member

@titusfortner titusfortner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were you able to build this to test that Selenium Manager works with the changes? I just created #12047 which could help with that.

dotnet/src/webdriver/SeleniumManager.cs Outdated Show resolved Hide resolved
dotnet/src/webdriver/SeleniumManager.cs Outdated Show resolved Hide resolved
@nvborisenko
Copy link
Member Author

CI for .net building already uses selenium manager (cannot put a link to PR cauze I am on mobile).

@nvborisenko
Copy link
Member Author

Ah, and yes, I have tested it locally.

@nvborisenko
Copy link
Member Author

Link to Pr where selenium manager is used for internal testing by default: #11871

@diemol diemol merged commit 5764ff9 into SeleniumHQ:trunk May 16, 2023
@fake119
Copy link

fake119 commented May 23, 2023

Hello. When would you deploy new binary with this fix?

@diemol
Copy link
Member

diemol commented May 23, 2023

End of May we plan to do a new release.

@NCLnclNCL
Copy link

Fix ?? Bro

@NCLnclNCL
Copy link

End of May we plan to do a new release.

When update bro

@titusfortner
Copy link
Member

soon. we'll announce it on our blog when it is ready — https://www.selenium.dev/blog/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants