We register custom protocol handler for our application.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Classes\testapp]
@="URL: TestApp Protocol"
"URL Protocol"=""
[HKEY_CURRENT_USER\SOFTWARE\Classes\testapp\shell]
[HKEY_CURRENT_USER\SOFTWARE\Classes\testapp\shell\open]
[HKEY_CURRENT_USER\SOFTWARE\Classes\testapp\shell\open\command]
@="\"wscript\" \"C:\\Users\\user1\\AppData\\Local\\Programs\\TestService\\CustomTestProtocolHandler.vbs\" \"%1\""
Wscript tool used to process the request.
Both Chrome and Explorer can start this custom protocol handler.
But it does not work from MS Edge.
Should I perform some additional configuration to enable custom protocol in Edge?
Or custom protocol handler which uses wscript will not work from MS Edge at all?
If we use cmd file instead of vbs then Edge can use this application protocol. But in this case Command Prompt window is be blinking during each request to this application protocol handler.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Classes\testapp]
@="URL: TestApp Protocol"
"URL Protocol"=""
[HKEY_CURRENT_USER\SOFTWARE\Classes\testapp\shell]
[HKEY_CURRENT_USER\SOFTWARE\Classes\testapp\shell\open]
[HKEY_CURRENT_USER\SOFTWARE\Classes\testapp\shell\open\command]
@="\"wscript\" \"C:\\Users\\user1\\AppData\\Local\\Programs\\TestService\\CustomTestProtocolHandler.vbs\" \"%1\""
Wscript tool used to process the request.
Both Chrome and Explorer can start this custom protocol handler.
But it does not work from MS Edge.
Should I perform some additional configuration to enable custom protocol in Edge?
Or custom protocol handler which uses wscript will not work from MS Edge at all?
If we use cmd file instead of vbs then Edge can use this application protocol. But in this case Command Prompt window is be blinking during each request to this application protocol handler.