BrowserFetcher downloads chromium by default to current directory (not to .dlls folder)

Description

BrowserFetcher.cs by default downloads chromium binaries to current working directory BroswerFetcher.cs

...
    DownloadsFolder = Path.Combine(Directory.GetCurrentDirectory(), ".local-chromium");
...

instead of to the directory where the binaries of project are located (as specified in BrowserFetcherOptions xml doc) BrowserFetcherOptions.cs

//...
       /// <summary>
       /// A path for the downloads folder. Defaults to [root]/.local-chromium, where [root] is where the project binaries are located.
       /// </summary>
       public string Path { get; set; }
//...

Expected behavior:

Either change the documentation, but better would be to download by default to the [root]/.local-chromium, where [root] is where the project binaries are located.

ie:

//...
    DownloadsFolder =
Path.Combine(Path.GetDirectoryName(Assembly.GetEntryAssembly().Location), 
".local-chromium");
//...

I can make PR for this - but the change is very small.

Versions

• Which version of PuppeteerSharp are you using? 1.10
• Which .NET runtime and version are you targeting? E.g. .NET framework 4.6.1 or .NET Core 2.0. happens on both

[videokojot]

I stumbled upon this because I am have simple PuppeteerSharp wrapper, which periodically kills zombie chromium processes (sometimes some of the puppeteer awaited calls just freeze outside of the managed code) and I wanted to be able to locate which process (or assembly) started it, to just kill those chromiums… I can account for this in my code (by setting the Path property in BrowserFetcher explictily)- but found the documentation was misleading…

@Meir017 I like this idea of enum & user profile cache folder.

[kblok]

Yes. but it would also would mean that if my app is at c:\myapp and I call it from c:\ or from c:\myapp\. Local-chromium would be always on c:\myapp\.local-chromium. Now we are creating two .local.chromium folders: one in c:\ and another in c:\myapp.