How do I prevent Microsoft.Web.WebView2 from generating a directory containing cache data, or how do I move it?

[ero (ero-qt)]

I have noticed that as soon as my C# application launches anything to do with Microsoft.Web.WebView2, a directory containing lots of cache data is generated next to my application. I do not want this, especially because the directory format is very confusing to users.

Is there a way to prevent this directory from being generated? Perhaps I can have it be generated in a more appropriate folder like %LocalAppData%?

[Richie Hindle (RichieHindle)]

The CoreWebView2CreationProperties.UserDataFolder property lets you control the location of the user data directory.

[Brian LaLonde (blalond)]

When creating:

tempUserDataFolder = Path.Combine(Path.GetTempPath(), "BrowserTemp", Guid.NewGuid().ToString());
Directory.CreateDirectory(tempUserDataFolder);

      CoreWebView2Environment env = await CoreWebView2Environment.CreateAsync(
                browserExecutableFolder: null,
                userDataFolder: tempUserDataFolder,
                options: options);
      await webView.EnsureCoreWebView2Async(env);

When closing:

private void WebView1_FormClosing(object? sender, FormClosingEventArgs e)
    {
        // Attempt to remove temporary user data folder if it exists
        if (!string.IsNullOrEmpty(tempUserDataFolder) && Directory.Exists(tempUserDataFolder))
        {
            try
            {
                var webViewProcessId = Convert.ToInt32(webView?.CoreWebView2.BrowserProcessId);
                var webViewProcess = System.Diagnostics.Process.GetProcessById(webViewProcessId);

                this.webView?.CoreWebView2.Profile.ClearBrowsingDataAsync();
                try { webView?.Dispose(); } catch { }

                // reference: https://stackoverflow.com/questions/70763018/how-to-delete-the-webview2-userdatafolder-in-c-sharp-wpf-application-browserpro
                // wait for process to exit with 3 second timeout
                webViewProcess.WaitForExit(3000);

                Directory.Delete(tempUserDataFolder, true);
            }
            catch
            {
                // best-effort: ignore failures to delete (files may be locked)
            }
        }
    }

[dca00]

Above are unacceptable solutions because having that much data being created and deleted every time the application starts increases the wear of storage media. This completely unnecessary bunch of 177 files in 67 folders and files has to have an option to be completely disabled.
All of that just for showing an HTML file to the user? Seriously?