Morph MORPH
SIGN IN SIGN UP
cefsharp / CefSharp UNCLAIMED

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

0 0 1 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>
<!-- <VisualStudioProductVersion Condition="'$(VisualStudioVersion)'=='15.0'">2017</VisualStudioProductVersion> -->
<!-- <VisualStudioProductVersion Condition="'$(VisualStudioVersion)'=='16.0'">2017</VisualStudioProductVersion> -->
<!-- <VisualStudioProductVersion Condition="'$(VisualStudioVersion)'=='16.0' AND Exists('$(SolutionDir)packages\$(CefSdkVer)\CEF\$(Platform)\$(Configuration)\VS2019\libcef_dll_wrapper.lib')">2019</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>
<!--<PlatformToolset Condition="'$(VisualStudioVersion)'=='14.0'">v140</PlatformToolset>
VS2017 Build with PlatformToolset v141 VC++2017(v141) is compatible with VC++2015(v140), which enables us to use the v141 toolset to compile against the v140 libcef_dll_wrapper.lib - not necessary to install the VC++2015 compiler as part of a clean VS2017 install Follow up to #2179
2017-12-20 10:21:08 +10:00
<PlatformToolset Condition="'$(VisualStudioVersion)'=='15.0'">v141</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
<PlatformToolset Condition="'$(VisualStudioVersion)'=='16.0'">v142</PlatformToolset>-->
<WindowsTargetPlatformVersion Condition="'$(VisualStudioVersion)'=='16.0'">10.0</WindowsTargetPlatformVersion>
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
<CefSharpBrowserSubprocessPostBuildEvent>
<![CDATA[
if $(PlatformName) == x86 (
"$(DevEnvDir)..\..\VC\bin\editbin" /largeaddressaware /TSAWARE "$(TargetPath)"
call "$(DevEnvDir)..\Tools\vsvars32.bat"
sn -R "$(TargetPath)" "$(ProjectDir)..\CefSharp.snk"
) else (
"$(DevEnvDir)..\..\VC\bin\amd64\editbin" /TSAWARE "$(TargetPath)"
)
]]></CefSharpBrowserSubprocessPostBuildEvent>
VS2019 build support with VS2017 toolset (#2816) * VS2019 build support with VS2017 toolset
2019-06-24 07:05:47 -05:00
<CefSharpBrowserSubprocessPostBuildEvent Condition="'$(VisualStudioVersion)'=='15.0' Or '$(VisualStudioVersion)'=='16.0'">
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
<![CDATA[
if $(PlatformName) == x86 (
call "$(DevEnvDir)..\..\VC\Auxiliary\Build\vcvars32.bat"
editbin /largeaddressaware /TSAWARE "$(TargetPath)"
sn -R "$(TargetPath)" "$(ProjectDir)..\CefSharp.snk"
) else (
call "$(DevEnvDir)..\..\VC\Auxiliary\Build\vcvars64.bat"
editbin /TSAWARE "$(TargetPath)"
)
]]>
</CefSharpBrowserSubprocessPostBuildEvent>
Use conditional elements to support VS2010.
2013-05-28 13:41:23 +02:00
</PropertyGroup>
</Project>
Reference in New Issue Copy Permalink