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

Funding Request - Release 57.0.0 #1963

Closed
amaitland opened this issue Feb 23, 2017 · 14 comments
Closed

Funding Request - Release 57.0.0 #1963

amaitland opened this issue Feb 23, 2017 · 14 comments
Milestone

Comments

@amaitland
Copy link
Member

amaitland commented Feb 23, 2017

For those interested in sponsoring a 57.0.0 release. Again a big thank you to everyone who supported the 55.0.0 release (#1893)

Rough details are as follows

  • A stable CEF build needs to appear on Spotify CEF Build Server (currently the there are no 2987 builds available yet).
  • When half of the funding target is met (and a viable build is available on Spotify CEF Build Server then a -pre release set of packages will be generated.

If the set BountySource target is not met then all is not lost, you can of course build your own Nuget packages and host then on your local feed.

More details will follow in the upcoming weeks.

Constructive comments welcome.

Bountysource

@peters
Copy link
Contributor

peters commented Mar 7, 2017

@amaitland This bounty has been funded :)

@amaitland
Copy link
Member Author

@amaitland This bounty has been funded :)

@peters Fantastic, thank you very much! 😄

@amaitland
Copy link
Member Author

amaitland commented Mar 13, 2017

master has been upgraded to 3.2987.1591, version number and relevant API changes were also made see e5ecfde for details.

  • BrowserSettings.CaretBrowsing has been removed
  • CefCustomScheme has two new properties IsSecure and IsCorsEnabled

There is a problem related to chrome_elf when using x64 builds. Based on the upstream comments I expect AnyCPU support to have problems when run on x64 machines (see bitbucket link below for details).
https://bitbucket.org/chromiumembedded/cef/issues/2122/windows-cef-2987-57-crashes-on-anycpu-x64

I've temporarily disabled the VS Hosting Process (26574eb) so the examples run.

@peters
Copy link
Contributor

peters commented Mar 13, 2017

@amaitland Excellent news! ;) Do you mind updating the package prefix on myget to 57-* ?

@amaitland
Copy link
Member Author

@amaitland Excellent news! ;) Do you mind updating the package prefix on myget to 57-* ?

Whoops! That's what happens when appveyor.yml is not part of the solution, fixed in a86e03b

@amaitland
Copy link
Member Author

General Usage Guide has been updated to include some new topics. Additional topic suggestions welcome.

@amaitland
Copy link
Member Author

There is a problem related to chrome_elf when using x64 builds. Based on the upstream comments I expect AnyCPU support to have problems when run on x64 machines (see bitbucket link below for details).
https://bitbucket.org/chromiumembedded/cef/issues/2122/windows-cef-2987-57-crashes-on-anycpu-x64

It looks like Chromium has reverted the changes that are causing the problems, see https://bugs.chromium.org/p/chromium/issues/detail?id=700371#c21 for details. Hopefully the next time CEF updates to a newer Chromium version the problem will be resolved.

@amaitland amaitland added this to the 57.0.0 milestone Mar 17, 2017
@amaitland
Copy link
Member Author

The upstream issue has been marked as resolved, a new build should hopefully appear on the Spotify build server in the next day or two, will upgrade soon as it's available. If all goes well then I'll publish a pre-release shortly after.

@amaitland
Copy link
Member Author

It looks like Chromium has reverted the changes that are causing the problems, see https://bugs.chromium.org/p/chromium/issues/detail?id=700371#c21 for details. Hopefully the next time CEF updates to a newer Chromium version the problem will be resolved.

master has been upgraded, the problem appears to be resolved (it's not possible to use x64 version with the VS hosting process again. so I expect AnyCPU will work as well.

I'll release the -pre in the next day or two

@amaitland
Copy link
Member Author

57.0.0-pre01 packages are on the MyGet feed see https://ci.appveyor.com/project/cefsharp/cefsharp/build/57.0.0-CI2225 for details.

They need a bit more testing then I'll upload them to Nuget.org.

@amaitland
Copy link
Member Author

57.0.0-pre01 have been pushed to Nuget.org, should appear in the next few hours.

@amaitland
Copy link
Member Author

cefsharp/57 has been upgraded to CEF 3.2987.1601 - Chromium 57.0.2987.133

Unless CEF pushes some important last minute bug fixes this will be the version the final release is based on. I'm aware that Print to PDF doesn't work in the current -pre release, that is fixed in the newer CEF version.

Will look at releasing the final packages in the next week.

@amaitland
Copy link
Member Author

57.0.0 Packages have been pushed to Nuget.org, they should appear shortly (takes a while before they're indexed)

Check out the Release Notes which as always includes a list of Known Issues. If you find a bug then please fill out the Issue Template when opening an issue.

I'll leave this open for a week to let the dust settle.

The MinimalExample project has also been upgraded as can be used for testing.

@amaitland
Copy link
Member Author

The latest generated API doc is available at http://cefsharp.github.io/api/57.0.0/

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

No branches or pull requests

2 participants