Closed
Description
CEF is dropping support for compiling the C++ wrapper with Visual Studio 2015/2017 see https://groups.google.com/g/cef-announce/c/IMgnaeWipwc/m/so6nGWgWBgAJ for details.
As a flow on from we will be forced to migrate from Visual C++ 2015 as the minimum to Visual C++ 2019 runtime. A lot of users will already have the Visual C++ 2015-2019 runtime, so no action will be required.
I will provide further updates once M93 builds are available and I can confirm exactly what changes are required.
- Update release notesUpdate General UsageUpdate FAQUpdate Readme.md
For those using the .Net Core 3.1/.Net 5.0
packages VC++ 2019
is already required.
Metadata
Metadata
Assignees
Type
Projects
Relationships
Development
No branches or pull requests
Activity
amaitland commentedon Jul 30, 2021
As per https://groups.google.com/g/cef-announce/c/IMgnaeWipwc/m/so6nGWgWBgAJ we should use
cef_callback.h
instead. https://github.com/cefsharp/CefSharp/blob/master/CefSharp.Core.Runtime/RequestContext.cpp#L17OVERRIDE
withoverride
(b24cd8e)NULL
withnullptr
(a18637f)Some of these changes will happen before upgrade to keep the changes in a single commit to a more reviewable size.
Branch https://github.com/cefsharp/CefSharp/tree/upgrade/93 has the work in process, it should compile, it won't run just yet. There is an incompatibility between our
C++/CLI
classes and the newIMPLEMENT_REFCOUNTING
implementation. It looks like the use ofatomic
forces the class to be a native class instead of amixed mode
class.There are also a lot of other cleanup tasks
amaitland commentedon Jul 30, 2021
Beta builds of version
93
are now available on https://cef-builds.spotifycdn.com/index.htmlAs expected attempting to build with
VS2015/VS2019
failed.As a result
CefSharp
will now requireVS2019
to compile,Visual C++ 2019
will now be the new minimum (Visual Studio 2022 is in preview and I expect that Visual C++ 2020 will be backwards compatible
).amaitland commentedon Jul 30, 2021
For those that have the
Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019
installed then no change will be required.For those that have an older
VC++ 2015/2017
installation there are a two options:VC++ 2019
dlls with your application (Local Deployment).Local Deployment
As you should already have the
Universal CRT
installed as you previous hadVC++ 2015/2017
installed (Universal CRT
is also included as part ofWindows 10
by default) you can bin deploy theVC++ 2019
dlls alongside your application.The following should copy the
VC++
runtime into the bin/publish folders when run underVisual Studio
(won't work from the command line). NOTE: ClickOnce will need different targets to add the files.For x86/x64:
For AnyCPU:
Visual C++ Runtime
Details on deploying/redistributing the
Visual C++ 2019 runtime
.Universal CRT
For those looking for more detail on the
Universal CRT
C++/CLI - Replace OVERRIDE with override
C++/CLI - Replace NULL with nullptr
build.ps1 - Remove older VS support
10 remaining items