-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Net Core/Net 5 - Enhancements #3388
Comments
- Remove x86/x64 platforms from the solution - Chromely.CefSharp.Integration.TestApp sets RuntimeIdentifier - Change TargetFrameworks to net462;netcoreapp3.1;net5.0-windows **KNOWN ISSUES** - The generated Nuget package has exclude buildTransitive set which will likely break the package (not tested, though very likely) The CefSharp.Common.NETCore.targets included in the buildTransitive has a hack to support AnyCPU which adds package references directly to the chromiumembeddedframework.runtime.win-x64 and chromiumembeddedframework.runtime.win-x86 packages Will need to add some configuration options to CefSharp to disable this behaviour, I've added a task to cefsharp/CefSharp#3388
- Remove x86/x64 platforms from the solution - Chromely.CefSharp.Integration.TestApp sets RuntimeIdentifier - Change TargetFrameworks to net462;netcoreapp3.1;net5.0-windows **KNOWN ISSUES** - The generated Nuget package has exclude buildTransitive set which will likely break the package (not tested, though very likely) The CefSharp.Common.NETCore.targets included in the buildTransitive has a hack to support AnyCPU which adds package references directly to the chromiumembeddedframework.runtime.win-x64 and chromiumembeddedframework.runtime.win-x86 packages Will need to add some configuration options to CefSharp to disable this behaviour, I've added a task to cefsharp/CefSharp#3388
- Remove x86/x64 platforms from the solution - Chromely.CefSharp.Integration.TestApp sets RuntimeIdentifier - Change TargetFrameworks to net462;netcoreapp3.1;net5.0-windows **KNOWN ISSUES** - The generated Nuget package has exclude buildTransitive set which will likely break the package (not tested, though very likely) The CefSharp.Common.NETCore.targets included in the buildTransitive has a hack to support AnyCPU which adds package references directly to the chromiumembeddedframework.runtime.win-x64 and chromiumembeddedframework.runtime.win-x86 packages Will need to add some configuration options to CefSharp to disable this behaviour, I've added a task to cefsharp/CefSharp#3388
Automatically deals with DPI Change Issue #3388
Automatically deals with DPI Change Issue #3388
Specific .Net core DependencyChecker that takes care of the specifics of running under .Net Core/.Net 5.0 Later on the DependencyChecker can be unified. Issue #3388
Specific .Net core DependencyChecker that takes care of the specifics of running under .Net Core/.Net 5.0 Later on the DependencyChecker can be unified. Issue #3388
https://github.com/cefsharp/CefSharp/blob/cefsharp/89/CefSharp/DependencyChecker.cs#L148 For The |
Follow up to #3197
There are a few things that I didn't quite get time for which should be done
WPF
DPI Changed handler (Window.DpiChanged).Net Core/Net 5
specificDependencyChecker
CefSharp.Common.NETCore.targets
to disable theOtherwise
block, when used in anAnyCPU
class library the dependencies added will flow through to the generatedNuget
package (using the default nuget pack option, not a problem if manual). (commit 5ebb08f)Potentially check
$(OutputType)
inMSBuild
is class library and disable this behaviour by default with an override to enableCefSharp.Common.NETCore
to includechromiumembeddedframework.runtime
asBuildTransitive
so the.props
files are usable as transitive reference. (commit 07ce2e0)NetCore
projects (currently .Net 4.5.2packages use
GitLink`) (commit 5780aef)The text was updated successfully, but these errors were encountered: