Resulting Setup.msi exits without any warning

[d9k]

I'm packing my electron app with electron-builder on Windows 7 x64. But when I try to execute resulting dist\win-x64\Setup.msi the installation process just exits without any message. How can I debug what goes wrong?
I tried to make my application "Squirrel Aware" just by copying code from http://www.mylifeforthecode.com/creating-a-windows-distribution-of-an-electron-app-using-squirrel/ but no luck (maybe it's outdated).
Also when I try another way and run dist\win-x64\MyApp-0.1.0.exe the application starts but I can't find whether application files were copied anywhere. And application state is not saved too. Application state and settings are intended to be stored at the settings.json which my application tries to create after settings changed or before exit. But when I run packaged MyApp-0.1.0.exe it "installs" again and no state is saved.

Am I asking the question at the wrong place? Should I create issue at electron-packager repo instead?
I have zero experience with Squirrel installers and lack of documentation exhausts me. Also packaging process is too long for understanding through experiments.

[develar]

Should I create issue at electron-packager repo instead?

Such questions should be addressed to https://github.com/electronjs/windows-installer

[develar]

Also packaging process is too long for understanding through experiments.

Consider to:

• build only one arch (--arch x64 (or ia32))
• if you don't need an MSI, set build.win.noMsi to true. See https://github.com/loopline-systems/electron-builder#distributable-format-configuration

[d9k]

@develar After running the builder with --arch x64 the dist/win-x64 folder is empty. (dist/win is not and it contains Setup.exe and Setup.msi) Is it normal behaviour?

[d9k]

@develar also I get dll linking error (as it was before you made extraResources support #230) when I run dist/win/Setup.exe which was made by builder --arch x64

[d9k]

@develar my package.json:

{
  "license": "proprietary",
  "private": true,
  "build": {
    "dir": "app",
    "win": {
        "extraResources": [
            "./*.dll"
        ]
    }
  },
  "scripts": {
    "postinstall": "install-app-deps",
    "start": "./node_modules/.bin/electron app",
    "dist": "./node_modules/.bin/build",
    "dist:win": "./node_modules/.bin/build --platform win32",
    "dist:x64": "./node_modules/.bin/build --arch x64"
  },
  "devDependencies": {
    "babel-cli": "^6.6.4",
    "babel-core": "^6.6.4",
    "babel-preset-es2015": "^6.6.0",
    "babel-preset-react": "^6.5.0",
    "babel-preset-stage-0": "^6.5.0",
    "babelify": "^7.2.0",
    "browserify": "^12.0.1",
    "electron-builder": "^2.10.1",
    "electron-prebuilt": "^0.36.0",
    "gulp": "^3.9.1",
    "gulp-babel": "^6.1.2",
    "gulp-concat": "^2.6.0",
    "gulp-notify": "^2.2.0",
    "gulp-sourcemaps": "^1.6.0",
    "gulp-util": "^3.0.7",
    "vinyl-source-stream": "^1.1.0",
    "watchify": "^3.6.1",
    "winreg": "0.0.13"
  }
}

When I run npm run dist:win it glitches too: no packages are made, only unpacked application files at dist/OrbiletClient-win32-ia32, dist/OrbiletClient-win32-x64. Tried again: no errors were shown, no packaged versions made.

[develar]

I filed electron/windows-installer#40

[d9k]

@develar thanks, what about issues with --arch x64 and --platform win32 arguments?
Am I the only person who experiences missing setup files after build with these arguments (I clean dist directory completely before build)?

[develar]

@d9k Is your last question fixed in the 3.0.1?

[d9k]

You mean different build options? I'll try later.

[d9k]

moved problems with arguments to separate issue #267