Repository navigation
Nuget - Remove netcoreapp3.0 hacks #3444
Copy link
Copy link
Closed
Description
Activity
Once
.Net 6.0is released (the nextLTSversion) I'll remove the hacks, looks like that'll be sometime inNovemberReacted by Konstantin PreißerI need to resolve #3706 which is blocked on this issue so I'm attaching this to the
95milestone. Little ahead of my original plan unfortunately.- added a commit that references this issue
on Oct 15, 2021 For
.Net Core 3.1/.Net 5.0+use the following packages:- https://www.nuget.org/packages/CefSharp.WinForms.NETCore
- https://www.nuget.org/packages/CefSharp.Wpf.NETCore
- https://www.nuget.org/packages/CefSharp.OffScreen.NETCore
- It is recommended that you set a
<RuntimeIdentifier/>during development, adding the following to your project file<RuntimeIdentifier Condition="'$(RuntimeIdentifier)' == ''">$(NETCoreSdkRuntimeIdentifier)</RuntimeIdentifier>will use the default for your operating system. Please read Feature Request - Add .Net 5.0 Support #3284 (comment) for more information. - For
.Net Core/.Net 5.0+theIjwhost.dllfile is required. To support C++/CLI libraries in .NET Core, ijwhost was created as a shim for finding and loading the runtime. All C++/CLI libraries are linked to this shim, such that ijwhost.dll is found/loaded when the C++/CLI library is loaded.
- added 2 commits that reference this issue
on Jan 7, 2025
As a temporary workaround whilst
.Net Core 3.1/.Net 5.0+support was being implemented some hacks were implemented to make theCefSharp.Wpf/CefSharp.WinForms/CefSharp.OffScreenpackages work easily with.Net Core 3.0. Now that we have a new set of packages and.Net Core 3.0is out of support we should remove the hacks. This will greatly reduce the size (approx 5mb reduction in size ofCefSharp.Commonas it has duplicate files).IMPORTANT
Anyone targeting
.Net Core 3.1/.Net 5.0+using these older packages will either need to migrate to the newer packages or try setting AssetTargetFallbackFor those targeting
.Net Core 3.0which are unable to upgrade to.Net Core 3.1 or greaterthen the old packages should still be usable by specifying AssetTargetFallback