Visual Studio WebView2 Debugger, cannot pass arguments

[karikera]

I'm not sure I can talk about the debugger here.

I want to pass some arguments to my WebView2 application.
So, I tried to use "Command Arguments" but they are replaced with other arguments.
Next, I tried to use "Environment" but they are removed or replaced also.
"Working Directory" also replaced with the application directory
I cannot find a way to solve this problem.

I want to debug the Emscripten WASM application with WebView2 debugger.
I created the tiny viewer with WebView2. but I cannot pass anything like the entry point of pages.

AB#28779839

[pagoe-msft]

Hi karikera,

Are you trying to pass arguments to the WebView2 like this: https://docs.microsoft.com/en-us/microsoft-edge/hosting/webview2/reference/webview2.idl#createwebview2environmentwithdetails ?

Or are you trying to send messages to your web content? If so, checkout out PostWebMessage API: https://docs.microsoft.com/en-us/microsoft-edge/hosting/webview2/reference/iwebview2webview#postwebmessageasjson

[karikera]

@pagoe-msft
Sorry about my bad English.

I'm trying to debug with the custom viewer on Visual Studio

[douglas-jordan]

The command line arguments in Visual Studio are not automagically passed as a parameter to any API call. You could write the code to take the command line passed to WinMain and use that as the command line arguments variable when creating the WebView2 Environment. However for testing purposes it would be easier to just pass the Environment a text string when its called.

[karikera]

@douglas-jordan
What I want - Put URI as an argument and navigate with the argument
What I can't - Pass the URI argument from Visual Studio Debugging to "emviewer.exe"(my custom viewer).
Why I can't - Command Arguments are replaced by other arguments. All Environment Variables are ignored. Working Directory is replaced by the directory of "emviewer.exe". (When Debugger Type == WebView2)
Don't want - Pass arguments to WebView2 Environment.

Sorry about my bad English.

[douglas-jordan]

The command line arguments are passed on to the executable by the debugger for testing purposes. You still have to write the code to handle command line processing in your application.

Command line for an executable:
https://docs.microsoft.com/en-us/windows/win32/learnwin32/winmain--the-application-entry-point

You will need to write the code that takes the executable command line and pass it to the WebView2 Environment - that text is appended to the default command line MSEDGE.EXE will use.

You will need to write the code that takes the executable command line (URI) and pass it to the WebView2->Navigate in order to use it.

[karikera]

Project: https://github.com/karikera/wv2debug

Configurations:

Expected Result:

argv[1]: https://rua.kr/
WV_ENTRY: https://rua.kr/
cwd: C:\

Actual Result:

[douglas-jordan]

I have looked at your code and this problem has nothing to do with WebView2.

[karikera]

[karikera]

I reported it to visual studio feedback, but They say It's an issue with WebView2.
https://developercommunity.visualstudio.com/content/problem/911613/webview2-debugger-cannot-pass-arguments-environmen.html

[champnic]

@douglas-jordan is correct - this isn't a WebView2 or VisualStudio bug - you just need to add handling for those arguments in your app for them to work properly.

[karikera]

I don’t know why it’s not possible to convey meaning.

There are no arguments to handle in the application when debugging.
It cannot pass any arguments to my application.
because all arguments are replaced by WebView2 debugger.

Is this English weird?

even I wrote sample code,
and I wrote actual value and expected value

I don't know what more I have to offer

[karikera]

The result is changed recently.

Pretty weird