求C#环境下无需用户预装浏览器的功能性无头浏览器解决方案

Great question! You’re right that Selenium’s dependency on pre-installed browsers and CefSharp’s limited out-of-the-box XPath support can be frustrating for distributing self-contained apps. Here are three robust C# solutions that meet your needs—self-contained binaries, no end-user browser installs, and full support for XPath, JS execution, and user interactions:

1. Playwright for .NET (Top Recommendation) #

Playwright is hands-down the most polished option here. It’s a modern automation framework that ships with its own browser binaries (Chromium, Firefox, WebKit) which you can bundle directly with your app. No need for users to install anything extra, and it supports all the features you need:

• XPath selectors (via Locator.XPath())
• JavaScript execution (Page.EvaluateAsync())
• Click/input events, form filling, and more
• Headless mode by default (or visible mode if needed)

Quick Example: #

using Microsoft.Playwright;

var playwright = await Playwright.CreateAsync();
await using var browser = await playwright.Chromium.LaunchAsync(new BrowserTypeLaunchOptions
{
    Headless = true,
    // Bundle the browser binary with your app: set this to your local binary path
    ExecutablePath = Path.Combine(AppContext.BaseDirectory, "chromium", "chrome.exe")
});

var page = await browser.NewPageAsync();
await page.GotoAsync("https://example.com");

// Use XPath to find an element and click it
var element = page.Locator("//a[text()='More information...']");
await element.ClickAsync();

// Execute JavaScript
var pageTitle = await page.EvaluateAsync<string>("document.title");
Console.WriteLine($"Page title: {pageTitle}");

When building your app, use the playwright install command to download browser binaries to your project directory, then include them in your deployment package for a fully self-contained build.

2. Puppeteer Sharp #

Puppeteer Sharp is the .NET port of Google’s Puppeteer framework, built specifically for Chromium. Like Playwright, it lets you bundle the Chromium binary with your app, so users don’t need to have Chrome installed. It supports:

• XPath queries (via Page.QuerySelectorAsync() with XPath syntax)
• JS execution (Page.EvaluateAsync())
• All standard user interactions (clicks, inputs, etc.)
• Headless mode

Quick Example: #

using PuppeteerSharp;

// Download Chromium binary if not present (run once during build)
await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultRevision);

var browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
    Headless = true,
    ExecutablePath = Path.Combine(BrowserFetcher.DefaultDownloadPath, BrowserFetcher.DefaultRevision, "chrome.exe")
});

var page = await browser.NewPageAsync();
await page.GoToAsync("https://example.com");

// Find element via XPath and click
var element = await page.QuerySelectorAsync("//a[text()='More information...']");
await element.ClickAsync();

// Run JavaScript
var pageUrl = await page.EvaluateAsync<string>("window.location.href");
Console.WriteLine($"Current URL: {pageUrl}");

await browser.CloseAsync();

Include the downloaded Chromium binaries in your app’s output directory to deliver a self-contained package users can run immediately.

3. Enhanced CefSharp (If You Prefer Embedded Browsers) #

You mentioned CefSharp lacks out-of-the-box XPath support, but you can easily add this functionality using JavaScript execution. CefSharp lets you run JS to query the DOM via XPath, then interact with elements through the script results. Here’s how:

Quick Example: #

using CefSharp;
using CefSharp.WinForms;

var chromeBrowser = new ChromiumWebBrowser("https://example.com");

// Wait for page to load
chromeBrowser.FrameLoadEnd += async (sender, args) =>
{
    if (args.Frame.IsMain)
    {
        // Execute XPath query via JavaScript
        var scriptResult = await chromeBrowser.EvaluateScriptAsync(@"
            function getElementByXPath(xpath) {
                return document.evaluate(xpath, document, null, XPathResult.FIRST_ORDERED_NODE_TYPE, null).singleNodeValue;
            }
            getElementByXPath('//a[text()=""More information...""]');
        ");

        if (scriptResult.Success && scriptResult.Result is IJsHandle elementHandle)
        {
            // Trigger click event on the element
            await elementHandle.EvaluateFunctionAsync("element => element.click()");
        }

        // Execute arbitrary JavaScript
        var titleResult = await chromeBrowser.EvaluateScriptAsync("document.title");
        Console.WriteLine($"Page title: {titleResult.Result}");
    }
};

CefSharp’s binaries can be included in your app package via NuGet, so users don’t need to install Chrome separately. This is a solid choice if you want an embedded browser UI (not just headless) while retaining automation capabilities.

All three options let you deliver a single binary package without requiring end-users to install any third-party software. Playwright is the most feature-complete and user-friendly, but Puppeteer Sharp or enhanced CefSharp work great if you have specific preferences.

内容的提问来源于stack exchange，提问作者RA.