ChrisCN wrote:What will be the final behavior?
Because this problem will also occur if I move the application to a different folder - or rename the folder and so on.
(We already talked about renaming the db-file and you mentioned that CN will know the new file after opening it).
Shouldn't the final version be similar stable in regards to the CN folder getting a new destination/name (we are still talking about a portable app)?
So if you get rid of the 'run as admin' dialog wouldn't it be a good idea to register on every start?
Unfortunately now we don't have enough time to implement this, but it future we'll put this straight.
The final behavior (in version 2.1 or so) will be approx as follows:
CN will remember in settings file if it has been registered as the link handler. If on start CN detects that it is not a link handler, although the settings file tells it otherwise, it will prompt the user to register the link protocol again.
The registering itself will be done as running another copy of itself with elevated privileges and a special command line parameter, so this instance will (after the user clicks on "Allow" on the UAC prompt that pops up) just register the protocol and exit.