How to use ToString method of PuppeteerSharp.ChromiumLauncher class

The issue was using Action instead of Func<Page, Task>.

Action always returns a void. Since the function Action was calling was a async method but was not sending the method's output it causes the function that called Action to exit which released the unmanged resources. The Func<Page, Task> retains the output so it can be awaited so the main thread is blocked till completion preventing the unmanaged resources from being release early.

async static void Main()
{
   Func<FileStream,Task> func = (FileStream fs) => Foo(fs); //Input to function is FileStream and Output of Function is Task
   Action<FileStream> action = (FileStream fs) => Foo(fs); //Equivalent to Func<FileStream , void>
   using var fs = new FileStream();
   //action(fs); //This can fail if the main thread is finished before it
   await func(fs); //This will succeed since the main thread is blocked till completion

}
async static Task Foo(FileStream fs) => await fs.SomeLongAsyncMethod();

Got it:
var localStorage = await page.EvaluateFunctionAsync<Dictionary<string, string>>("async () => Object.assign({}, window.localStorage)");

The execution of the GetCookiesAsync task needs to be awaited, like this:

private async Task YourMethod()
{ 
    var result = await page.GetCookiesAsync();
}

You might need to change your callers for this.

Try to read about asynchronous programming in C#: https://learn.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/async/

So what you are seeing with this:

Id = 7315, Status = WaitingForActivation, Method = "{null}", Result = "{Not yet computed}"

is the async task not yet completed. GetCookiesAsync returns immediately. If you want to want to wait for the result, you should await it.

Not sure you can disable the built in download manager with --disable-extensions.

Another approach if it is just ZIP's you want to stop is to plumb this code in:-

await page.setRequestInterception(true);
page.on('request', request => {
    if (request.url().endsWith('.zip'))
        request.abort();
    else
      request.continue();
});

You may also want to lower case the url so you also trap .ZIP abnd Zip etc

Also on your goto you will need to abort the request e.g.

  await page
        .goto("https://winaero.com/downloads/Win7Games4Win10_8_81_v2.zip")
        .catch(r => r.abort);

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

Based on Line 43 of the LanchOptions.cs you can specify arguments to the launch process.

Now connecting this with the native JavaScript (using the --load-extension flag) the output should look similar to the following:

var browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
    Args = new string[1] { "--load-extension=/Path/To/Extension/Folder" }
});

Note: that I put path to folder, not the .zip as you have in your sample.. if you want to load multiple extensions then just separate the paths using a comma.

Here's a full list of possible arguments that can be passed in to Chromium.

First, the evaluate function won't get what you write in the console.log. You need to return something. As you are waiting for an event you can return a promise and resolve that promise inside the event.

page.EvaluateFunctionAsync<Point>(@"() => {
  return new Promise(resolve => {
    document.onmousemove = function(e){
      mouseX = e.offsetX;
      mouseY = e.offsetY;
      resolve({x: mouseX, y: mouseY});
    };
  });
}");

For anybody still encountering this issue, the answer by jamie-tillman on this github issue solved it for me:

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
#####################
#PUPPETEER RECIPE based on https://github.com/hardkoded/puppeteer-sharp/issues/1180#issuecomment-1015532968
#####################
RUN apt-get update && apt-get -f install && apt-get -y install wget gnupg2 apt-utils
RUN wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | apt-key add -
RUN echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' >> /etc/apt/sources.list
RUN apt-get update \
&& apt-get install -y google-chrome-stable --no-install-recommends --allow-downgrades fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-freefont-ttf
######################
#END PUPPETEER RECIPE
######################
ENV PUPPETEER_EXECUTABLE_PATH "/usr/bin/google-chrome-stable"
WORKDIR /app
EXPOSE 80
EXPOSE 443

The path to the executable is automatically detected by Puppeteer. However, I still had to disable sandboxmode as seen in the snippet below:

var browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
    Headless = true,
    Args = new [] {
      "--disable-gpu",
      "--disable-dev-shm-usage",
      "--disable-setuid-sandbox",
      "--no-sandbox"}
});

More useful information is found in the issue thread so I recommend skimming through it if you still have trouble.

For anybody still encountering this issue, the answer by jamie-tillman on this github issue solved it for me:

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
#####################
#PUPPETEER RECIPE based on https://github.com/hardkoded/puppeteer-sharp/issues/1180#issuecomment-1015532968
#####################
RUN apt-get update && apt-get -f install && apt-get -y install wget gnupg2 apt-utils
RUN wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | apt-key add -
RUN echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' >> /etc/apt/sources.list
RUN apt-get update \
&& apt-get install -y google-chrome-stable --no-install-recommends --allow-downgrades fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-freefont-ttf
######################
#END PUPPETEER RECIPE
######################
ENV PUPPETEER_EXECUTABLE_PATH "/usr/bin/google-chrome-stable"
WORKDIR /app
EXPOSE 80
EXPOSE 443

The path to the executable is automatically detected by Puppeteer. However, I still had to disable sandboxmode as seen in the snippet below:

var browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
    Headless = true,
    Args = new [] {
      "--disable-gpu",
      "--disable-dev-shm-usage",
      "--disable-setuid-sandbox",
      "--no-sandbox"}
});

More useful information is found in the issue thread so I recommend skimming through it if you still have trouble.