I have an electron app and now I need to get an executable file for it.
I am worried which tool to use electron-builder or electron-forge.
I tried to use electron-builder and configuration it, because I need to install the app with steps like accepting eula license agreement, select folder for installation, ask for running after the installation finished etc. It looks like everything work with electron-builder and its very easy.
My question is can I do the same configs using electron-forge or the only way is to package with electron-forge and then build a single setup EXE file using for example INNO SETUP COMPILER ( and do those configs via INNO SETUP ) ?
The second: Which tool is the best for auto updates?
For the auto updates you can check this one Electron - autoUpdater
Related
I'm trying to follow other people who had a similar issue like this one
Electron-Builder include external folder I wish i could be more specific on what my problem is, the reason is that i dont know whats wrong.
I am making a react app which has a server with an sqlite db and im trying to use electron.js to make it into an installable/executable
here is my dummy repo https://github.com/Juan321654/electron_react_with_build_installer_sqlite_db the master branch was just how to make electron work with react, the server branch is the one that i need help with
you can clone and just do npm i, npm run start to launch executable. npm run build to build
the code works fine in development mode and even after i make the build project with electron i can launch the executable and it works fine and it reads the data from the database, but as soon as i take the dist folder out of the project to send to someone or install the software, it stops working and it loads the app, but it does not read the data from the server/db, I am not sure if its missing node modules or the server folder, or maybe if im missing some kind of command in my scripts in the package.json?
I am trying to sign all executables + dll files in my application, within an Azure Pipeline, using Azure signtool for that. (doing basically the described here) - on the result of running dotnet publish.
Exception is updater.exe, because it is generated by Advanced Installer API or some other proprietary way. Signing the updater.exe file that lies inside Advanced Installer installation folder /x86/updater.exe - does not help (it will work, but the updater.exe that is deployed when installing the MSI is not signed, meaning it is generated during processing of the .AIP file, which happens after running dotnet publish)
Is there a way the updater.exe AI generates (with the custom icon, etc) to be created using AdvancedInstaller.com command line API ? How ?
The question has already been answered in the forums here:
https://www.advancedinstaller.com/forums/viewtopic.php?f=5&t=50297#p127034
I have an application packaged and signed as an MSIX, it installs and runs from the start menu. I'd like to be able to run the application from the command line too, for automated testing, but I can't see a way to do it. From powershell the docs suggest Invoke-CommandInsideDesktopPackage, but that requires developer mode which I'd rather not enable on test machines, and also is not the same as just running the app. What I'd love is a simple command line command that starts the app in the same way that the start menu does it.
By design, the binaries from an installation folder of an MSIX folder are not directly accessible through their direct path.
The correct way to run an app from the command line from an MSIX package is with the use of an execution alias. The following article contains more details about how an execution alias works and how you can define it in your package, no matter the tool you use to build the MSIX package.
- App Execution Alias
Also, here is a related question on SO.
I have built application .exe installer using electron-builder and JavaScript.
I am trying to set up environment variable during or right after the installation of the application. It will hold value of the installation directory of the application chosen by the user during the install wizard.
I am very much stuck, can you share some ideas on this please?
Thanks
I've just built an app with Electron.
Installing and running electron-packager . creates a folder my-app-win32-x64 with a bunch of assets and DLLs.
This isn't exactly something I can distribute to consumers.
What's the simplest way to generate a Windows installer for my electron executable?
It looks like according to their wiki you can. Follow the instructions here! https://github.com/electron/windows-installer
You may try electron-wix-msi it will help you to create a exe file.
it will basically ask you for your source file Path example D:\xyz\my-app-win32-x64
and will create a desired file at app source path.