- Use the application exe instead of CefSharp.BrowserSubprocess.exe
- M103 will add a new CefSharpExcludeSubProcessExe which will
exclude the exe from builds
- Old example is still there for reference, just not used by default
- Add AsyncContext/SingleThreadSynchronizationContext to ensure async calls continue on main thread.
* Upgrade to 94.4.20
- WinForms/Wpf/OffScreen - Update app.manifest
- Change version number to 1.0.0.0 (from 65.0.0.0) as it was never updated
- Update DPI awareness for WPF/OffScreen
* Upgrade to 91.1.60-pre
* AnyCPU - Use the new CefRuntime.SubscribeAnyCpuAssemblyResolver method
Now CefSharp.dll is an AnyCPU dll the code for AnyCPU dll resolution can be added to the library.
Exact same code, just included in CefSharp.dll
* Upgrade to 91.1.160
* Upgrade to 91.1.210
* Upgrade to v88.2.40-pre
WPF - Add https scheme to default URL to workaround upstream issue
https://bitbucket.org/chromiumembedded/cef/issues/3079/cant-load-urls-without-scheme
* Net Core - Add AnyCPU Platform to projects/solution
* Net Core - Add RuntimeIdentifier based on PlatformTarget
- Set RuntimeIdentifier based on PlatformTarget (PlatformTarget isn't set of AnyCPU)
- Set SelfContained to false so as not to provide a Framework Dependant build (don't include the whole .net framework)
* WPF/WinForms - Change CefSharpBuildAction to Content
For testing of ClickOnce publish
* Net 5.0 - Update to include PublishSingleFile settings
- .Net 5.0 Publish Settings for PublishSingleFile
https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file
Defaults differ compared to .Net Core 3.1
- Set RollForward to Major so runs on newer runtime version
- Add net5.0-windows TargetFramework
* .Net 5.0 - Publish Single Exe Example
- Use the main application exe as the BrowserSubprocess when self publishing a .Net 5.0 exe
- Only the WPF and WinForms examples have been updated
https://github.com/cefsharp/CefSharp/issues/3407
* Upgrade to 88.2.90
