Morph MORPH
SIGN IN SIGN UP
cefsharp / CefSharp UNCLAIMED

.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework

0 0 0 C#
Normal View History Raw
VS2017 build support (using the VS2015 tooling) (#2179) * initial vs2017 build support * update nuget retrieval url apparently http://nuget.org/nuget.exe is version 2.8, which is fairly old * enable child process debugging
2017-11-29 21:47:39 +01:00
<?xml version="1.0" encoding="utf-8"?>
Use conditional elements to support VS2010.
2013-05-28 13:41:23 +02:00
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
Update to M93 (#3781) * Upgrade to CEF 93.1.7+g9117d6a+chromium-93.0.4577.42 / Chromium 93.0.4577.42 - Core - Add basic ref counting implementation IMPLEMENT_REFCOUNTING implementation uses atomic which forces the VC++ compiler to compile as native which doesn't work for our managed ref classes. - Use InterlockedCompareExchange for custom ref count reads - Use InterlockedIncrement/InterlockedDecrement directly - There's no memory barrier for HasOneRef/HasAtLeastOneRef as the read of a LONG should happen in one operation on 32/64 bit architectures (at least that's my understanding at this point in time). References: https://github.com/chromiumembedded/cef/blob/4472/include/base/internal/cef_atomicops_x86_msvc.h#L125 https://github.com/chromiumembedded/cef/blob/4472/include/base/internal/cef_atomicops_arm64_msvc.h#L107 https://github.com/chromiumembedded/cef/blob/4472/include/base/cef_atomic_ref_count.h#L114 https://github.com/chromiumembedded/cef/blob/4472/include/cef_base.h#L91 - Remove Microsoft.Net.Compilers package from projects Now that we require a min of VS2019 to build there's no need for a custom compiler package - Start removing VS2015/VC++2015 references - Remove RegisterWidevineCdm This is a breaking change. CEF will now automatically download the Widevine CDM component Resolves #3767 - RequestContext.LoadExtension now uses managed to code spawn on CEF UI Thread Avoid having to use cef_callback.h which was causing problems for x86 builds
2021-09-03 10:51:18 +10:00
<VisualStudioProductVersion>2019</VisualStudioProductVersion>
Fix Visual Studio 2022 support (#4346) Co-authored-by: Michael Stoll <michael.stoll@stolltec.com>
2022-12-20 20:27:02 +01:00
<VisualStudioProductVersion Condition="'$(VisualStudioVersion)'=='17.0' AND Exists('$(SolutionDir)packages\$(CefSdkVer)\CEF\$(Platform)\$(Configuration)\VS2022\libcef_dll_wrapper.lib')">2022</VisualStudioProductVersion>
Use conditional elements to support VS2010.
2013-05-28 13:41:23 +02:00
Update to M93 (#3781) * Upgrade to CEF 93.1.7+g9117d6a+chromium-93.0.4577.42 / Chromium 93.0.4577.42 - Core - Add basic ref counting implementation IMPLEMENT_REFCOUNTING implementation uses atomic which forces the VC++ compiler to compile as native which doesn't work for our managed ref classes. - Use InterlockedCompareExchange for custom ref count reads - Use InterlockedIncrement/InterlockedDecrement directly - There's no memory barrier for HasOneRef/HasAtLeastOneRef as the read of a LONG should happen in one operation on 32/64 bit architectures (at least that's my understanding at this point in time). References: https://github.com/chromiumembedded/cef/blob/4472/include/base/internal/cef_atomicops_x86_msvc.h#L125 https://github.com/chromiumembedded/cef/blob/4472/include/base/internal/cef_atomicops_arm64_msvc.h#L107 https://github.com/chromiumembedded/cef/blob/4472/include/base/cef_atomic_ref_count.h#L114 https://github.com/chromiumembedded/cef/blob/4472/include/cef_base.h#L91 - Remove Microsoft.Net.Compilers package from projects Now that we require a min of VS2019 to build there's no need for a custom compiler package - Start removing VS2015/VC++2015 references - Remove RegisterWidevineCdm This is a breaking change. CEF will now automatically download the Widevine CDM component Resolves #3767 - RequestContext.LoadExtension now uses managed to code spawn on CEF UI Thread Avoid having to use cef_callback.h which was causing problems for x86 builds
2021-09-03 10:51:18 +10:00
<PlatformToolset>v142</PlatformToolset>
VS2022 - Very basic support for VS2022 Opening either solution in VS2022 should no longer prompt to upgrade VC++ version/Win10 SDK. Having both VS2019 and VS2022 installed might be a problem if VS2022 doesn't have the required components installed. Update .vsconfig Win10 SDK version to 19041 (same as Chromium requires for build)
2021-12-08 10:45:31 +10:00
<PlatformToolset Condition="'$(VisualStudioVersion)'=='17.0'">v143</PlatformToolset>
Update to M93 (#3781) * Upgrade to CEF 93.1.7+g9117d6a+chromium-93.0.4577.42 / Chromium 93.0.4577.42 - Core - Add basic ref counting implementation IMPLEMENT_REFCOUNTING implementation uses atomic which forces the VC++ compiler to compile as native which doesn't work for our managed ref classes. - Use InterlockedCompareExchange for custom ref count reads - Use InterlockedIncrement/InterlockedDecrement directly - There's no memory barrier for HasOneRef/HasAtLeastOneRef as the read of a LONG should happen in one operation on 32/64 bit architectures (at least that's my understanding at this point in time). References: https://github.com/chromiumembedded/cef/blob/4472/include/base/internal/cef_atomicops_x86_msvc.h#L125 https://github.com/chromiumembedded/cef/blob/4472/include/base/internal/cef_atomicops_arm64_msvc.h#L107 https://github.com/chromiumembedded/cef/blob/4472/include/base/cef_atomic_ref_count.h#L114 https://github.com/chromiumembedded/cef/blob/4472/include/cef_base.h#L91 - Remove Microsoft.Net.Compilers package from projects Now that we require a min of VS2019 to build there's no need for a custom compiler package - Start removing VS2015/VC++2015 references - Remove RegisterWidevineCdm This is a breaking change. CEF will now automatically download the Widevine CDM component Resolves #3767 - RequestContext.LoadExtension now uses managed to code spawn on CEF UI Thread Avoid having to use cef_callback.h which was causing problems for x86 builds
2021-09-03 10:51:18 +10:00
VS2022 - Very basic support for VS2022 Opening either solution in VS2022 should no longer prompt to upgrade VC++ version/Win10 SDK. Having both VS2019 and VS2022 installed might be a problem if VS2022 doesn't have the required components installed. Update .vsconfig Win10 SDK version to 19041 (same as Chromium requires for build)
2021-12-08 10:45:31 +10:00
<!-- TODO: We might need to do something here when VS2019 and VS2022 are installed -->
BrowserSubProcess - Increase x64/arm64 stack size - For Net 4.5.2 it appears we need to resign the exe - For .Net Core as the exes are native it doesn't look like we need to sign them (the CefSharp.BrowserSubprocess.dll is actually the one that's signed). - Remove unused CefSharpBrowserSubprocessPostBuildEvent Issue #3986
2022-03-01 15:05:28 +10:00
<WindowsTargetPlatformVersion>10.0</WindowsTargetPlatformVersion>
<!-- <WindowsTargetPlatformVersion Condition="'$(VisualStudioVersion)'=='16.0'">10.0</WindowsTargetPlatformVersion> -->
<!-- <WindowsTargetPlatformVersion Condition="'$(VisualStudioVersion)'=='17.0'">10.0</WindowsTargetPlatformVersion> -->
Use conditional elements to support VS2010.
2013-05-28 13:41:23 +02:00
</PropertyGroup>
</Project>
Reference in New Issue Copy Permalink