Using WebView2 with Office or VSIX projects fails with default UserDataFolder creation

[champnic]

Description

Currently, when WebView2 is launched in an Office add-in or as part of a VSIX project, the default UserDataFolder (if no UserDataFolder path is specified) gets created under "C:\Program Files (x86)...". This causes the WebView2 to fail to initialize because it doesn't have write permissions at that location. The workaround is to specify a separate UserDataFolder, but this is cumbersome and shouldn't be required by default.

Version
SDK: all
Runtime: all
Framework: WPF in Office/Visual Studio contexts
OS: all

Additional context
Relevant GitHub issues:
#195 (comment)
#195 (comment)
#505
https://github.com/MicrosoftEdge/WebView2Feedback/issues?q=is%3Aissue+VSTO+
https://github.com/MicrosoftEdge/WebView2Feedback/issues?q=is%3Aissue+VSIX

@yannduran FYI

AB#29901610

[DavidShoe]

We have a fix in active development. No release ETA yet, but we are working it.

[yannduran]

@DavidShoe

OMG I can't wait to be able to use WebView2 in a VS extension, even for something as basic as displaying web or XML content! I don't need all the bells and whistles.

[champnic]

Please see our update here: #1410 (comment)

[yannduran]

@DavidShoe , @champnic - so is this going to happen or not? Are we going to be able to use WebView2 out of the box, no extra fiddling in a Visual Studio VSIX extension? Now that VS 2022 has deprecated the internal browser control based on ancient IE, we need this more now than ever!

I couldn't see anything following the link you posted about this.