Puppeteer-sharp

You can use different browser instances for each logical instances. I mean instead of trying to set different proxy for each page/tab with different proxy just create new browser instance and set proxy via launch args.

If this solution doesn't fit your needs, check this question. There is library for NodeJS which give ability to use different proxy per each page/tab. You can check that library source code and implement same things inside your C# application.

That library is using very simple method. Instead of sending requests via puppeter's browser/page library send request via nodejs http tools. It can be done by using method page.setRequestInterception. So library intercept each request from page, after that gather data and send request via http tools. I used C# a long time ago. So maybe I am wrong, but you can try to use HttpWebRequest or something similar. After you get result you should use method request.respond and pass response results there. In this way you can put any kind of proxy inside your application. Check here code of library.

I found a lib called puppeteer, and it has .net version puppeteer-sharp.

I made a stupid typo when searching answers from other people. Actually, it was simple. The launch option has some wrong text, delete the http:// is enough, since I am using direct IP address. So the correct syntax is:

rivate static readonly LaunchOptions puppeteer_launchOptions = new LaunchOptions 
{
Headless = false,
IgnoreHTTPSErrors = true,
    Args = new [] {
        "--proxy-server=1.2.3.4:5678",
        "--no-sandbox",
        "--disable-infobars",
        "--disable-setuid-sandbox",
        "--ignore-certificate-errors",
    },

};

By the way, --disable-infobars seems not working since 1.19.0 until 1.20.0; I always see the information: Chrome is being controlled by automated test software. I remember someone said since 1.19.0 Google Chrome changed something, so --disable-infobars not working, but he also provide some example how to disable the warning, but his method did NOT include PuppeteerSharp, Puppeteer was included. Now, I can't figure it out yet.
Hope my question can help some other people. It is just a typo, not a big issue!

You could use a using block for that:

public static async Task<string> renderHtmlAsync(string url2)
{
    await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultChromiumRevision);
    using (Browser browser = await Puppeteer.LaunchAsync(new LaunchOptions
    {
        Headless = true
    }))
    {
        var page = await browser.NewPageAsync();
        page.DefaultTimeout = 0;
        var navigation = new NavigationOptions
        {
            Timeout = 0,
            WaitUntil = new[] {
                    WaitUntilNavigation.DOMContentLoaded }
        };
        await page.GoToAsync(url2, navigation);
        var content = page.GetContentAsync();

        return await content;
    }
}

This works like:

var myObject = new DispoableObject();
try
{
    // insert code
    return result;
}
finally
{
    myObject.Dispose();
}

The code in the finally is always executed, even when an exception is thrown inside the try block.

If you are using CSS selector as a locator then you haven't provided correct locator.

You can try following CSS Selector which should work.

Using Type attribute

await page.ClickAsync("button[type='submit']");

OR Using name attribute

 await page.ClickAsync("button[name='login-submit']");

OR using class attribute

await page.ClickAsync("button.inline-btn-2");

OR Using multiple attribute such as

await page.ClickAsync("button[type='submit'][name='login-submit']");

using below,

using var page = browser.NewPageAsync().Result;

page.TypeAsync("input[name='elementname']", valuetobeset).Wait();

For local path, need to use file protocol like below:

await page.GoToAsync("file://" + Path.Combine(context.FunctionAppDirectory, "www", "index.html"));

After reading this issue, it seems that we should use absolute path with UserDataDir, so this works fine:

browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
    Headless = true,
    UserDataDir = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, ".local-chromium", "Win64-884014", "chrome-win", "UserData").Replace(@"\", @"\\")
});

But another problem appeared because browser doesn't save any cookie. Again, some issues on github said that the browser should be closed in order to save the cookies. I tried this:

await page.CloseAsync();
await browser.CloseAsync();

But it doesn't works as expected because the browser is still running in the background. The final solution for my was this:

var chromes = System.Diagnostics.Process.GetProcesses().Where(x => x.ProcessName == "chrome").ToList();

foreach (var ch in chromes)
{
    try
    {
        ch.Kill();
    }
    catch
    {
    }
}

The above code will close all chrome browsers, so it may need some changes in order to close the current browser only.

I am thinking something like this should probably work - It takes the Stream that gets returned by the 'ScreenshotStreamAsync' method of the page and copies it to a MemoryStream so that we can get a byte array out of it really simply and pass that byte array to the Convert.ToBase64String

var thing =  await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultRevision);
        var browser = await Puppeteer.LaunchAsync(new LaunchOptions
        {
            Headless = false
        });
        var page = await browser.NewPageAsync();

        await page.SetViewportAsync(new ViewPortOptions
        {
            Width = 750,
            Height = 750,
        });

        await page.SetContentAsync("<h2>Test</h2>");
        await page.ScreenshotAsync(@"test1.jpg");

        using (var memStream = new MemoryStream())
        {
           page.ScreenshotStreamAsync().Result.CopyTo(memStream);
           var mything = Convert.ToBase64String(memStream.ToArray());
           Console.WriteLine(mything);
        }