Protocol (scheme) for windows

• Version: 5.4.2

• Target: Windows

I’m trying to build my application for OSX and for Windows. Right now my package.json looks like below:

"build": {
    "appId": "",
    "app-category-type": "",
    "dmg": {},
    "win": {
      "iconUrl": ""
    },
    "protocols": [
      {
        "name": "App name",
        "schemes": ["myapp"]
      }
    ]
  }

So everything working for OSX and I can open application using myapp:// scheme. How can I make the same for Windows?

[ghost]

I figured out my problem. I didn’t set the installer to perMachine: true, so it was installing for a single user, and apparently the registry keys don’t work in that case.

[hacdias]

@develar this is quite easy to implement via the NSIS script. I’m using the following macro to make it work:

!macro AddProtocolHandler Protocol Description
  DeleteRegKey SHELL_CONTEXT "Software\Classes\${Protocol}"
  WriteRegStr SHELL_CONTEXT "Software\Classes\${Protocol}" "" "${Description}"
  WriteRegStr SHELL_CONTEXT "Software\Classes\${Protocol}" "URL Protocol" ""
  WriteRegStr SHELL_CONTEXT "Software\Classes\${Protocol}\DefaultIcon" "" "$appExe,0"
  WriteRegStr SHELL_CONTEXT "Software\Classes\${Protocol}\shell" "" ""
  WriteRegStr SHELL_CONTEXT "Software\Classes\${Protocol}\shell\open" "" ""
  WriteRegStr SHELL_CONTEXT "Software\Classes\${Protocol}\shell\open\command" "" "$appExe %1"
!macroend

And then I just call it for each protocol. It could be done here for the protocols defined in the Build configuration.