Setting start path to Update.exe does not work

[marcindanek85]

• The target platform(s) the problem occurs on (Linux, Mac, Mac App Store, and or Windows): Windows 8.1

• Node version (run node -v): 6.3.0

• auto-launch version: 5.0.1

• The options you're passing to auto-launch: var AutoLaunch = require("auto-launch");

  var appLauncher = new AutoLaunch({
  name: "Trampoline"
  });

• Are you using NW.js or Electron? Electron

  • If so, which version? "1.6.6"
  • If you're using Electron, are you using auto-launch from the main process or a renderer process? main process

• Can you reproduce this with a simple Hello World example app? haven't tried yet

• If needs be, would you be able to provide us with a simple app (as simple as possible) which reproduces the problem? will prepare one

---

The issue is, that calling appLauncher.enable() creates registry entry pointing to executable path. It documentation there is info, that squirrel should be detected and path to Update.exe should be set. Is it true? What should I set, that auto-launch detect squirrel?

Additionaly, if I set name and path (calculated path do the Update.exe --processStart trampoline.exe) i get such entry in registry: Update.exe --processStart trampoline, but the name is set to Trampoline... It seems to be ignored and taken from appPath with removing ending .exe...

EDIT: it cannot work, as paths are set in fixOpts function, that sets for windows invalid path and entry name.

[adam-lynch]

Right now, auto-launch doesn't support passing additional arguments. The work to support this has been started on #47.

But, I don't think we do anything special our Teamwork Chat Windows desktop app (which updates via Squirrel). Right @4ver?

[marcindanek85]

I've reviewed the source code of the auto-launch a few weeks ago, and all this code was implemented, but was overwritten on some level, and all the logic, that is specific to Windows, was lost. I've rewritten it quickly in typescript. If you are interesed - I can share the source code with You.