Skip to content

Copy arm64 files for AnyCpu builds - #5288

Open
M4ttsson wants to merge 1 commit into
cefsharp:netarm64from
M4ttsson:netarm64-anycpu
Open

Copy arm64 files for AnyCpu builds#5288
M4ttsson wants to merge 1 commit into
cefsharp:netarm64from
M4ttsson:netarm64-anycpu

Conversation

@M4ttsson

Copy link
Copy Markdown

Addition to PR: #5267
Fixes: #4155

Summary:

  • Adds arm64 AnyCPU build targets to the NuGet/CefSharp.Common.targets‎ using same layout as for x86 & x64 builds.

Changes:

  • Adds CefSharpTargetDirAnyCpuArm64, resolving to arm64\.
  • In the CefSharpBuildAction=None AnyCPU path, adds ARM64 copies for:
    • @(CefRedistArm64) — CEF redistribution/native resources
    • @(CefSharpCommonBinariesArm64)CefSharp.Core.Runtime.dll, browser subprocess files, etc.
    • @(CefSharpCommonManagedDll)CefSharp.dll, required by the architecture-specific browser subprocess folder
  • Adds the same three ARM64 copy rules to the CefSharpBuildAction=Content AnyCPU path.

How Has This Been Tested?

  1. Built the CefSharp NuGet packages locally from the netarm64 branch including my changes
  2. Configured a .NET Framework 4.8.1 WPF test application to restore CefSharp.Wpf 150.0.110 from that local package feed.
  3. Built the test application as AnyCPU, project file included the following.
    <CefSharpAnyCpuSupport>true</CefSharpAnyCpuSupport> <CefSharpPlatformTargetOverride>AnyCPU</CefSharpPlatformTargetOverride> <PreferNativeArm64>true</PreferNativeArm64
  4. Verified the AnyCPU build output contains all three runtime folders
  5. Deployed the AnyCPU output to a native Windows ARM64 VM. The application startup log reported:
    Process architecture: Arm64 Expected runtime: ...\arm64\CefSharp.Core.Runtime.dll Expected CEF runtime: ...\arm64\libcef.dll

I also validated these changes the same way in our product’s cefsharp-browser application: it builds as AnyCPU with the ARM64 CefSharp runtime included and prefers native ARM64 execution on supported Windows devices.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Updated documentation

Checklist:

  • Tested the code(if applicable)
  • Commented my code
  • Changed the documentation(if applicable)
  • New files have a license disclaimer
  • The formatting is consistent with the project (project supports .editorconfig)

@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 05c9c99b-52a9-4dee-99fc-62ea40791079

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@AppVeyorBot

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants