Blame: CefSharp.BrowserSubprocess/CefSharp.BrowserSubprocess.netcore.csproj - cefsharp/CefSharp

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

0 0 1 C#

Net Core - Support for compiling with .Net Core 3.1 - Make Wpf/WinForms/OffScreen projects target AnyCPU Only the VC++ projects are platform specific now. - Remove BrowserSubProcess project reference Not needed as we now have a standalone exe - Add OffScreen example - Add WPF Example project - Fix some compile errors for main solution - Add BrowserSubProcess executable - JavascriptObjectRepository remove isAsync param Rather than throw exception remove the option - BrowserSubprocess Exclude the WCF specific code from the netCore project - Add some ifdef/ifndef to exclude the WCF specific implementation - Move WCF implementation into separate namespace 2020-07-18 13:30:54 +10:00			`<?xml version="1.0" encoding="utf-8"?>`
			`<Project>`
			`<!-- Note: We cannot use the recommended style of specifying <Project Sdk=...> because we need`
			`to set BaseIntermediateOutputPath and BaseOutputPath before the SDK props are imported. -->`
			`<PropertyGroup>`
			`<BaseIntermediateOutputPath>obj.netcore\</BaseIntermediateOutputPath>`
			`<BaseOutputPath>bin.netcore\</BaseOutputPath>`
			`</PropertyGroup>`

			`<!-- Implicit top import -->`
			`<Import Project="Sdk.props" Sdk="Microsoft.NET.Sdk" />`

			`<PropertyGroup>`
			`<OutputType>WinExe</OutputType>`
Core - Build BrowserSubProcess for net6.0-windows - This is only for local builds, we still only ship a .Net Core 3.1 exe (.Net 5.0 for arm64) - Potentially we should always use the netcoreapp3.1 exe to mimic what's happening when using the nuget packages That would require changes to the .targets file to copy the correct exe based on arch 2023-03-13 13:25:11 +10:00			`<TargetFrameworks>netcoreapp3.1;net5.0-windows</TargetFrameworks>`
			`<TargetFrameworks Condition="'$(VisualStudioVersion)'=='17.0'">$(TargetFrameworks);net6.0-windows</TargetFrameworks>`
Net Core - Support for compiling with .Net Core 3.1 - Make Wpf/WinForms/OffScreen projects target AnyCPU Only the VC++ projects are platform specific now. - Remove BrowserSubProcess project reference Not needed as we now have a standalone exe - Add OffScreen example - Add WPF Example project - Fix some compile errors for main solution - Add BrowserSubProcess executable - JavascriptObjectRepository remove isAsync param Rather than throw exception remove the option - BrowserSubprocess Exclude the WCF specific code from the netCore project - Add some ifdef/ifndef to exclude the WCF specific implementation - Move WCF implementation into separate namespace 2020-07-18 13:30:54 +10:00			`<RootNamespace>CefSharp.BrowserSubprocess</RootNamespace>`
			`<AssemblyName>CefSharp.BrowserSubprocess</AssemblyName>`
			`<GenerateAssemblyInfo>false</GenerateAssemblyInfo>`
			`<SignAssembly>true</SignAssembly>`
			`<AssemblyOriginatorKeyFile>..\CefSharp.snk</AssemblyOriginatorKeyFile>`
			`<CodeAnalysisRuleSet>MinimumRecommendedRules.ruleset</CodeAnalysisRuleSet>`
			`<ApplicationManifest>app.manifest</ApplicationManifest>`
			`<StartupObject>CefSharp.BrowserSubprocess.Program</StartupObject>`
Add support for Windows ARM64 to CefSharp.NETCore packages (#3359) * Add support for Windows ARM64 for the NETCore packages. Note: .NET 5.0 or higher is required to build a WinForms/WPF application for win-arm64. Fixes cefsharp/CefSharp#2944 * PR feedback: Remove "WIN32" define as it is already defined by minwindef.h. * PR feedback: Switch the CefSharp..Example.netcore and CefSharp.Test.netcore projects from cef.redist to chromiumembeddedframework.runtime. Note: These projects are excluded for build when platform is 'arm64', as otherwise the build fails as WinForms and WPF are not yet available for ARM64 in .NET 5.0. Follow-Up: Update path to CefSharp.Test.dll. * PR feedback: Also use RuntimeInformation for the .NET Framework example projects. * PR feedback: - Remove copying of CefRedist files in CefSharp.AfterBuild.targets which is no longer needed. - Update .vsconfig to include the VC ARM64 build tools. 2021-04-01 09:27:48 +02:00			`<Platforms>x86;x64;arm64</Platforms>`
			`<!-- Explicitly set the PlatformTarget for arm64, see: https://github.com/dotnet/sdk/issues/15434 -->`
			`<PlatformTarget Condition="'$(Platform)' == 'arm64'">arm64</PlatformTarget>`
Net Core - BrowserSubProcess run on newer .Net version Set RollForward Major so if .Net Core 3.1 isn't installed then .Net 5 can be used (if installed) Issue #3197 2020-12-16 13:36:44 +10:00			`<!--`
			`Run on a newer version of .Net if the specified version (.Net Core 3.1) is not installed`
			`https://github.com/dotnet/docs/issues/12237`
			`-->`
			`<RollForward>Major</RollForward>`
Net Core - Support for compiling with .Net Core 3.1 - Make Wpf/WinForms/OffScreen projects target AnyCPU Only the VC++ projects are platform specific now. - Remove BrowserSubProcess project reference Not needed as we now have a standalone exe - Add OffScreen example - Add WPF Example project - Fix some compile errors for main solution - Add BrowserSubProcess executable - JavascriptObjectRepository remove isAsync param Rather than throw exception remove the option - BrowserSubprocess Exclude the WCF specific code from the netCore project - Add some ifdef/ifndef to exclude the WCF specific implementation - Move WCF implementation into separate namespace 2020-07-18 13:30:54 +10:00			`</PropertyGroup>`

Net Core - BrowserSubprocess compile as x86/x64 variants Using an AnyCPU process wouldn't load when the browser process was x86 Basically x86 browser process couldn't use an x64 subprocess Issue #3197 2020-11-06 17:41:45 +10:00			`<PropertyGroup Condition="'$(Configuration)'=='Debug'">`
Net Core - Support for compiling with .Net Core 3.1 - Make Wpf/WinForms/OffScreen projects target AnyCPU Only the VC++ projects are platform specific now. - Remove BrowserSubProcess project reference Not needed as we now have a standalone exe - Add OffScreen example - Add WPF Example project - Fix some compile errors for main solution - Add BrowserSubProcess executable - JavascriptObjectRepository remove isAsync param Rather than throw exception remove the option - BrowserSubprocess Exclude the WCF specific code from the netCore project - Add some ifdef/ifndef to exclude the WCF specific implementation - Move WCF implementation into separate namespace 2020-07-18 13:30:54 +10:00			`<WarningLevel>2</WarningLevel>`
			`</PropertyGroup>`

Net Core - Embed PDB and Source For release builds we embed project source and symbols (at least until https://github.com/dotnet/sdk/issues/1458 is resolved) Issue #3197 2020-11-06 15:45:36 +10:00			`<PropertyGroup Condition="'$(Configuration)'=='Release'">`
			`<EmbedAllSources>True</EmbedAllSources>`
			`<DebugType>embedded</DebugType>`
			`</PropertyGroup>`

Net Core - Support for compiling with .Net Core 3.1 - Make Wpf/WinForms/OffScreen projects target AnyCPU Only the VC++ projects are platform specific now. - Remove BrowserSubProcess project reference Not needed as we now have a standalone exe - Add OffScreen example - Add WPF Example project - Fix some compile errors for main solution - Add BrowserSubProcess executable - JavascriptObjectRepository remove isAsync param Rather than throw exception remove the option - BrowserSubprocess Exclude the WCF specific code from the netCore project - Add some ifdef/ifndef to exclude the WCF specific implementation - Move WCF implementation into separate namespace 2020-07-18 13:30:54 +10:00			`<ItemGroup>`
			`<Compile Remove="bin\**" />`
			`<Compile Remove="obj\**" />`
			`<EmbeddedResource Remove="bin\**" />`
			`<EmbeddedResource Remove="obj\**" />`
			`<None Remove="bin\**" />`
			`<None Remove="obj\**" />`
			`</ItemGroup>`
			`<ItemGroup>`
			`<Compile Remove="Program.cs" />`
			`</ItemGroup>`
			`<ItemGroup>`
			`<ProjectReference Include="..\CefSharp.BrowserSubprocess.Core\CefSharp.BrowserSubprocess.Core.netcore.vcxproj" />`
			`<ProjectReference Include="..\CefSharp\CefSharp.netcore.csproj" />`
			`</ItemGroup>`

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			`<Target Name="PostBuild" AfterTargets="PostBuildEvent">`
Use decimal instead of hexadecimal notation for the stack size with the "editbin /STACK:" command, to work-around a regression introduced in editbin v14.33 (and possibly 14.32 or 14.31) that no longer recognizes the "0x..." hex format. (#4241) See https://github.com/cefsharp/CefSharp/discussions/4231 2022-09-07 21:06:35 +02:00			<Exec Command="if $(PlatformName) == x86 ( call "$(DevEnvDir)..\..\VC\Auxiliary\Build\vcvars32.bat" editbin /largeaddressaware /TSAWARE "$(TargetDir)CefSharp.BrowserSubprocess.exe" ) else if $(PlatformName) == x64 ( call "$(DevEnvDir)..\..\VC\Auxiliary\Build\vcvars64.bat" editbin /STACK:8388608 "$(TargetDir)CefSharp.BrowserSubprocess.exe" ) else if $(PlatformName) == arm64 ( call "$(DevEnvDir)..\..\VC\Auxiliary\Build\vcvarsamd64_arm64.bat" editbin /STACK:8388608 "$(TargetDir)CefSharp.BrowserSubprocess.exe" ) " />
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			`</Target>`

Net Core - Support for compiling with .Net Core 3.1 - Make Wpf/WinForms/OffScreen projects target AnyCPU Only the VC++ projects are platform specific now. - Remove BrowserSubProcess project reference Not needed as we now have a standalone exe - Add OffScreen example - Add WPF Example project - Fix some compile errors for main solution - Add BrowserSubProcess executable - JavascriptObjectRepository remove isAsync param Rather than throw exception remove the option - BrowserSubprocess Exclude the WCF specific code from the netCore project - Add some ifdef/ifndef to exclude the WCF specific implementation - Move WCF implementation into separate namespace 2020-07-18 13:30:54 +10:00			`<!-- Implicit bottom import -->`
			`<Import Project="Sdk.targets" Sdk="Microsoft.NET.Sdk" />`
			`</Project>`